Showing 0 products
What communication and navigation systems guide aircraft during runway approach and landing?
How do air traffic control networks coordinate runway usage and prevent incursions?
Roles and coordination: Ground controls all taxiways/movement areas; Local (Tower) controls runways and takeoffs/landings; Approach/Departure sequences flows and hands off to Tower; Ramp controls non-movement areas. Handoffs use standardized phraseology, readback/hearback, and electronic flight strips. Letters of Agreement and runway-use programs define configurations and crossing points.
Clearances and separation: Only Tower issues “enter/line up and wait/takeoff/land/cross runway” clearances. One active clearance per runway segment; explicit runway designators required. Time- or distance-based separation, anticipated runway occupancy time (ROT) management, conditional clearances prohibited in many states. Runway crossings require explicit clearance for each runway.
Information sharing: ATIS/D-ATIS for weather/runway status; NOTAMs for closures/works; SWIM/CDM share demand/capacity data; PDC/CPDLC reduces frequency congestion; standard taxi routes and hotspots published on charts.
Surveillance and alerts: Surface radar and multilateration (SMR/ASDE-X/ADS-B) provide real-time surface tracks. Safety nets (RIMCAS/ASDE-X alerts/TAWS taxi alerts) warn of conflicts. Runway Status Lights (RELs, THLs) and Stop Bars/Runway Guard Lights provide automatic, controller-independent cues. Final Approach Runway Occupancy Signal (where installed) warns arriving aircraft of occupied runways.
Visual aids and procedures: Markings, signage, lighting per ICAO/FAA standards; SMGCS/low-visibility procedures with stop bars and follow-me vehicles; progressive taxi on request; LAHSO where authorized with stringent minima.
Vehicles and personnel: Movement-area access control, dedicated vehicle frequencies, driver training/certification, discrete transponder codes, and mandatory position reports.
Human factors and safety management: Standard phraseology, complete readbacks of hold-short/runway instructions, sterile cockpit on movement areas, memory aids/runway status boards, recurrent training, incident reporting/LOSA, and runway inspections/FOD sweeps.
Together these layered procedures, surveillance, lighting, and communication protocols coordinate runway usage and prevent incursions.
How is real-time runway status and closure information shared (e.g., ATIS, NOTAM, A-SMGCS)?
What sensors and surveillance systems monitor runway surfaces and movements (radar, ADS-B, multilateration)?
These feed A‑SMGCS Level 1–4 functions for surveillance, routing, guidance, and safety nets (e.g., incursion/conflict alerts).
How are weather and runway condition reports (RVR, braking action) collected and disseminated?
Weather observations: Automated systems (ASOS/AWOS) and certified observers measure wind, visibility, ceiling, temperature/dew point, pressure, present weather. Data updates at least hourly (METAR) and on significant change (SPECI). Dissemination: METAR/SPECI, ATIS/D-ATIS, VOLMET, ACARS/CPDLC, AFTN/SWIM, flight-planning portals.
RVR (Runway Visual Range): Measured on equipped runways by transmissometers or forward-scatter sensors located at touchdown, midpoint, and rollout zones. Algorithms factor runway light intensity, background luminance, and sensor extinction to produce RVR in feet/meters, updating at least once per minute. Dissemination: included in METAR/SPECI (e.g., R28/1800FT), ATIS/D-ATIS, controller voice advisories on request/when required, and data link. Availability depends on runway equipment status.
Braking action/Runway condition:
• Airport operations conduct runway condition assessments during/after precipitation or when contamination is suspected, inspecting each third of the runway for contaminant type, depth, and coverage. Using ICAO GRF/FAA RCAM, they assign Runway Condition Codes (RWYCC 0–6) per third; friction devices may be used for situational awareness but are not sole determinants.
• Pilot braking action reports (good/medium/poor/nil) supplement ground assessments; ATC issues Braking Action Advisories when reports are less than “good.”
• Dissemination: Field Condition NOTAMs (FICON, U.S.) or SNOWTAM (ICAO) list contaminants, depths/percent, treatments, and RWYCC by thirds; ATIS/D-ATIS and controller broadcasts highlight significant changes; pilot reports are relayed on frequency and entered in PIREP systems.
Update cadence: RVR continuously; METAR hourly/SPECI as needed; runway condition reports whenever conditions change materially, after treatment, or at prescribed inspection intervals; new FICON/SNOWTAM supersedes prior.
What roles do 5G and IoT play in smart runway operations and maintenance?
How are airport communication networks and runway systems protected against cyber threats?