Fatal LaGuardia Runway Collision Lays Bare Systemic Gaps in Surface Safety Architecture
Two Jazz Aviation pilots are dead after an Air Canada Express CRJ-900 struck a Port Authority ARFF vehicle on Runway 4 in the worst fatal accident at the airport in three decades — raising urgent questions about ATC workload, ASDE-X alert performance, and whether a decade of runway safety investment has been enough.
At approximately 23:40 ET on March 22, 2026, Air Canada Express Flight 8646 — a Jazz Aviation Bombardier CRJ-900LR arriving from Montréal — struck a Port Authority Aircraft Rescue and Firefighting (ARFF) vehicle on Runway 4 at New York LaGuardia Airport (LGA), killing both pilots and injuring 41 others. The ARFF truck had been cleared by ATC to cross the active landing runway in response to a simultaneous emergency involving a United Airlines aborted takeoff; the clearance was rescinded seconds too late. LaGuardia — equipped with both ASDE-X surface surveillance radar and FAA Runway Status Lights — was operating under night VMC with mist and rain. The NTSB has deployed a Go-Team and is leading the investigation with support from Canada's Transportation Safety Board. ATC staffing levels at the time of the accident, Safety Logic alert performance, and ARFF vehicle coordination protocols are all under investigative scrutiny. The accident is the first fatal commercial runway collision in the United States since the 2025 Reagan National mid-air.
The Collision Sequence
Flight AC8646, a Bombardier CRJ-900LR registered C-GNJZ and operated by Jazz Aviation on behalf of Air Canada Express, completed a routine one-hour service from Montréal-Pierre Elliott Trudeau International Airport (YUL) before touching down on Runway 4 at LaGuardia at approximately 23:37 local time. Carrying 72 passengers and four crew members, the aircraft was decelerating along the runway when it encountered a Port Authority ARFF vehicle crossing at Taxiway Delta — directly in the landing path.
Air traffic control audio recorded by LiveATC.net and ATC.com captured the sequence with stark clarity. In the recording, the ARFF vehicle radio operator transmits: "Truck 1 and company LaGuardia Tower requesting to cross 4 at Delta." The controller issues the crossing clearance. Seconds later — apparently realizing the Air Canada aircraft was still rolling on the runway — the same controller is heard transmitting: "Stop, stop, stop, Truck 1, stop, stop, stop." The collision occurs before the truck can comply.
FAA Administrator Bryan Bedford confirmed that the ARFF vehicle had been dispatched to respond to United Airlines Flight 2384, a Boeing aircraft that had aborted its takeoff on the opposite side of the airport after an anti-ice warning light illuminated and crew reported a cabin odor that sickened flight attendants. The United crew declared an emergency when no gate was immediately available. The ARFF vehicle was authorized to cross Runway 4 at Taxiway Delta to reach the United aircraft — placing it directly in the path of the decelerating CRJ-900.
FlightRadar24 preliminary data indicated the Air Canada aircraft was traveling between 93 and 105 mph at the point of impact, though a second Flightradar24 data point cited by Reuters placed ground speed at approximately 24 mph at last contact. NBC News law enforcement sources cited approximately 30 mph at collision. The discrepancy will be resolved by the Flight Data Recorder, which the NTSB is analyzing.
"The two pilots who were killed were young men at the start of their career. This is an absolute tragedy."
— FAA Administrator Bryan Bedford, Press Conference, LaGuardia Airport, March 23, 2026The nose section of the CRJ-900 bore the full force of impact. The height differential between the relatively low-slung regional jet and the mass of the heavy ARFF truck concentrated crash energy at the cockpit. Both the captain and first officer — neither yet publicly identified — were pronounced dead at the scene. Forty-one people were transported to Queens hospitals: 39 from the aircraft and two Port Authority ARFF officers, both hospitalized in stable condition with broken bones. CBS News law enforcement sources reported one passenger suffered a traumatic brain bleed; a flight attendant, strapped in her seat, fell through an opening in the severed forward fuselage. Nine passengers remained hospitalized as of Monday afternoon, some with serious injuries. An unaccompanied minor aboard was reunited with family, Port Authority Executive Director Kathryn Garcia confirmed.
ATC Coordination and the Simultaneous Emergency Problem
The accident exhibits what aviation safety professionals recognize as a classic concurrent-emergency failure mode: a controller simultaneously managing two separate crises on opposite sides of the airport field — a declared emergency on one runway and an active landing on another — authorizing a crossing movement without adequate deconfliction of the two operations.
Aviation safety analysts who reviewed available ATC audio noted that the controller appears to have been managing both local tower and ground control functions. Reports citing aviation experts suggest the possibility that a single controller was working combined positions, though Transportation Secretary Sean Duffy pushed back on this characterization at a Monday afternoon press conference, stating that reports of a sole controller were "not accurate." Duffy declined, however, to specify how many controllers were on duty or whether combined positions were in use. He confirmed that LGA has 33 certified controllers against a target of 37 and seven controllers in training — a shortfall of four certified controllers at one of the nation's busiest airports.
The FAA confirmed to TIME magazine that ATC staffing levels at LaGuardia at the time of the collision "will be part of the investigation." NTSB Chair Jennifer Homendy and Member John DeLeeuw are serving as on-scene spokespersons for the investigation. The Transportation Safety Board of Canada has also deployed a team, as the aircraft was registered in Canada and operated by a Canadian carrier. The Air Line Pilots Association International (ALPA) dispatched representatives to support the NTSB.
Investigative Focus Areas — NTSB Go-Team Per available reporting and standard NTSB investigative protocols for runway incursion accidents, the Go-Team's inquiry is expected to examine: ATC staffing levels and position consolidation practices at time of collision; ASDE-X Safety Logic alert status and any generated alarms; Runway Status Light status at Taxiway Delta; ARFF vehicle ADS-B/transponder equipment and multilateration tracking coverage; ATC display configuration and controller situational awareness; FAA Order JO 7110.65 runway crossing clearance procedures; and weather conditions, including reported mist, rain, and standing water on Runway 4.
Surface Surveillance Infrastructure: What Was There, What Should Have Triggered
LaGuardia is among the 35 U.S. airports equipped with the FAA's Airport Surface Detection Equipment, Model X (ASDE-X) — a multi-sensor fusion system that integrates surface movement radar, multilateration, and ADS-B to produce a continuously updated positional picture of all aircraft and vehicles on the airport movement area. The FAA's ASDE-X program, the successor to the ASDE-3/AMASS (Airport Movement Area Safety System) architecture deployed at major airports through the 1990s and 2000s, includes a conflict detection and alerting module known as Safety Logic, which is designed to detect converging tracks and issue both visual and aural alerts to tower controllers.
LaGuardia is additionally equipped with FAA Runway Status Lights (RWSL) — an independent, automated pavement-embedded safety system fed by the ASDE-X data stream that illuminates red Runway Entrance Lights at taxiway-runway intersections when an aircraft is detected as active on the runway. The RWSL system is specifically designed to provide an automated, controller-independent warning directly to ground vehicle operators at the stop bar — the precise scenario that unfolded at Taxiway Delta on Sunday night.
ASDE-X is explicitly designed to track non-transponder-equipped vehicles through its surface movement radar component — the radar element provides skin-track returns from large metallic ground vehicles regardless of whether those vehicles carry cooperative ADS-B or transponder equipment. A Port Authority ARFF truck is a large, highly radar-reflective target; at X-band or Ka-band surface surveillance frequencies, it would generate a strong return. The fusion of radar skin-track data with any available multilateration or ADS-B information from the truck would then feed into Safety Logic's conflict detection algorithms.
Those questions were answered at the NTSB's first full on-scene press briefing Monday afternoon. NTSB Chair Homendy confirmed that the FAA Technical Center's analysis of the ASDE-X replay is unambiguous: "ASDE-X did not generate an alert due to the close proximity of vehicles merging and unmerging near the runway, resulting in the inability to create a track of high confidence." Homendy confirmed she reviewed the replay herself and observed two radar blobs — skin-track returns only, with no identification data — on Taxiway Delta. Neither target was seen crossing in front of the aircraft on the replay. The Runway Status Lights were reported as functioning per the replay, though the NTSB stated that finding requires verification by FAA Technical Operations.
The root cause of the ASDE-X failure is direct and damning: Truck 1 carried no transponder. Homendy confirmed there was no indication that any of the ARFF vehicles involved carried transponders. Without a cooperative track, ASDE-X's Safety Logic was operating on radar skin-returns only. As multiple ARFF vehicles staged near Taxiway Delta in the seconds before the crossing clearance — merging and unmerging as the convoy prepared to move — the track-management algorithms could not maintain a high-confidence track on any individual vehicle. The Safety Logic conflict detection algorithm requires stable, identified tracks to compute conflict geometry; with only ambiguous, merging radar blobs, no alert fired. This is precisely the nuisance-suppression failure mode that engineers on the original ASDE-3/AMASS program identified decades ago: the system cannot reliably discriminate between a threat and clutter when ground vehicles cluster near runway thresholds without cooperative identification data.
The ATC Staffing Context
The accident occurred against a backdrop of well-documented, chronic ATC understaffing that has been the subject of congressional inquiry, union advocacy, and a formal National Academies of Sciences study released in June 2025. That report found that ATC facility shortages were attributable to past hiring constraints and a misallocated workforce, compounded by inefficiencies in shift scheduling, and that failure rates for achieving full certification at individual facilities were increasing — particularly at large facilities handling the most complex commercial traffic.
The National Air Traffic Controllers Association (NATCA) has reported that before the current DHS partial government shutdown — now in its sixth week — approximately 40 percent of FAA facilities required six-day workweeks at least once per month, with some requiring them every week. "The working conditions have become consistently unsafe for those in the sky, as well as the physical and mental health of the controllers," wrote one controller in a NASA Aviation Safety Reporting System submission reviewed by CNN. A February 9, 2026 letter to FAA Administrator Bedford, signed by 14 members of Congress, cited increased reliance on overtime and expressed concern that mandatory overtime to cover staffing gaps was creating fatigue conditions inconsistent with safe operations.
The NTSB's afternoon briefing resolved some of the staffing ambiguity while adding new dimensions of concern. Homendy confirmed there were exactly two people in the tower cab at the time of the collision: the local controller and the controller in charge. The local controller had signed on at 10:45 p.m. for a shift ending at 6:45 a.m.; the controller in charge had signed on at 10:30 p.m. for a shift ending at 6:30 a.m. Critically, Homendy confirmed the controller in charge was simultaneously performing clearance delivery duties — a third functional role. Who was performing ground controller duties remains unresolved: the NTSB reported conflicting information, with some records indicating the controller in charge and others indicating the local controller. That ambiguity is itself an investigative finding, and the NTSB noted it would begin controller interviews at 4:00 p.m. Monday.
Homendy confirmed that operating with two controllers on the midnight shift — with those two performing the combined duties of local control, ground control, clearance delivery, and controller-in-charge oversight — is standard operating procedure at LaGuardia for the midnight shift, and is common practice across the national airspace. She explicitly stated that the NTSB's ATC team has raised concerns about this practice for years, and signaled that whether a 900-flight-per-day airport like LaGuardia should be subject to the same two-controller midnight SOP as lower-volume facilities will be a specific focus of this investigation. The NTSB also noted conflicting dates and times on the facility logs — an evidentiary inconsistency that investigators must reconcile before the staffing picture is definitive.
The midnight shift dimension adds a fatigue layer to the staffing picture. Homendy noted that the NTSB has identified the midnight shift as a concern in multiple prior investigations, specifically because it spans the circadian low — the period of maximum human fatigue during the 24-hour cycle. She was careful to state there is no current indication fatigue was a factor in this specific accident, but its presence as a variable is undeniable: the collision occurred just before midnight at the beginning of the midnight watch, with a controller who had signed on only 15 minutes earlier and may not yet have been fully situated in the position. The NTSB also raised unresolved questions about shift relief — the controller was still on duty for several minutes after the collision when he normally would have been relieved, and the NTSB is investigating whether anyone was available to relieve him.
At the Monday afternoon press conference, Transportation Secretary Duffy acknowledged that ATC infrastructure modernization requires additional congressional appropriation. "It's not a partisan issue; both Democrats and Republicans agree, but they have to have the will to finish the funding," he said, adding that he was not asserting the crash could have been prevented with full modernization — but that safety demands investment.
Historical Resonance: A Pattern Repeating
Aviation safety professionals have been quick to note the structural similarities between Sunday's collision and the February 1, 1991 runway disaster at Los Angeles International Airport, in which USAir Flight 1493 — a Boeing 737 — struck SkyWest Flight 5569, a Fairchild Metroliner holding on Runway 24L. All 12 occupants of the commuter aircraft and 22 of 89 aboard the 737 died. The NTSB's probable cause finding in that accident — that Los Angeles ATC facility management failed to implement procedures providing redundancy, and that the local controller lost situational awareness while managing simultaneous competing demands — reads with uncomfortable familiarity in the context of Sunday night's events. In the 1991 accident, the LAX surface radar was inoperative due to a maintenance failure and parts obsolescence that had persisted for years despite management warnings, eliminating what would have been the primary technological backup to controller situational awareness.
The 1991 accident directly catalyzed the NTSB's 1991 recommendation that the FAA develop an automated system to bring controller and pilot attention to pending runway incursions before collision — a recommendation that, through a decade of MIT Lincoln Laboratory development, eventually produced both the ASDE-X Safety Logic and the RWSL programs. LaGuardia was one of the airports identified for RWSL deployment. The technology the nation invested in after 1991 was in place Sunday night. Whether it performed as designed is now the central question of the NTSB investigation.
This is also not LaGuardia's first close call in recent years. In May 2025, a Republic Airways aircraft operating for American Airlines aborted takeoff to avoid a United Airlines plane still on the runway — an event that prompted FAA and NTSB inquiries. NTSB documentation from 2007 records a separate runway incursion at LGA involving Delta and Comair aircraft on Runway 22. The recurrence pattern at a single facility is itself an investigative data point.
Aircraft, Operator, and Regulatory Framework
The CRJ-900LR is a proven 76-seat regional jet in wide service across North American carriers. Jazz Aviation, LP — headquartered in Halifax, Nova Scotia — is Canada's largest regional carrier and a wholly owned subsidiary of Chorus Aviation Inc., operating exclusively under the Air Canada Express brand. Jazz is certificated by Transport Canada under Canadian Aviation Regulations and operates to FAA/DOT Part 121 equivalent standards when flying in U.S. airspace. The aircraft, C-GNJZ, was delivered new to Jazz in 2005.
Air Canada CEO Michael Rousseau addressed the accident in a video statement Monday: "We are deeply saddened by the loss of two Jazz employees, and our deepest condolences go out to the Jazz community and their families." Jazz President Doug Clarke issued a statement calling it "an incredibly difficult day for our airline, our employees, and most importantly the families and loved ones of those affected." Air Canada has established a passenger and family assistance hotline at 1-800-961-7099.
The FAA confirmed that Canadian authorities — the Transportation Safety Board of Canada (TSB) and Transport Canada — will participate in the investigation under ICAO Annex 13 protocols, given the Canadian registration of the aircraft and the Canadian nationality of the operator. However, since the collision occurred on U.S. soil, the NTSB holds accredited investigative authority and will produce the probable cause finding.
Insurance sources told Reuters that Global Aerospace leads the all-risks cover for the Air Canada regional aircraft; Marsh is the broker. The insured hull value is approximately $10 million. Passenger liability exposure, given the serious injuries and two fatalities, is substantially larger and will involve the complex intersection of U.S. federal tort claims, Montreal Convention limits, Port Authority sovereign immunity questions under New York law, and potential FAA negligence claims under the Federal Tort Claims Act.
NTSB Initial Briefing: The Confirmed Record — Second Day On Scene
NTSB Chair Jennifer Homendy and investigator Doug Brazy delivered the board's first substantive on-scene briefing Monday afternoon. The session produced several confirmed findings of immediate significance, superseding earlier speculation on key investigative questions.
Recorders. Both the Cockpit Voice Recorder and Flight Data Recorder were taken into NTSB possession at 9:57 a.m. Monday. The aircraft was equipped with an Acron Aviation model Survivor 25 CVR and an Acron Aviation model FA21000 FDR. The CVR contained more than 25 hours of good-quality audio across four channels. The FDR contained approximately 80 hours of data recording more than 400 parameters. An NTSB CVR group convened Tuesday at headquarters in Washington to produce a written transcript; FDR download and group analysis began the same day.
The CVR Timeline — Final Three Minutes. Brazy read the following sequence from the CVR, referenced to the end of recording. At 3 minutes 7 seconds: approach control instructed the crew to contact LaGuardia Tower. At 2 minutes 45 seconds: landing gear lowered. At 2 minutes 22 seconds: crew checked in with LaGuardia Tower. At 2 minutes 17 seconds: LaGuardia Tower cleared the aircraft to land on Runway 4 and advised it was number two for landing. At 1 minute 52 seconds: flaps set to 30 degrees. At 1 minute 33 seconds: flaps set to 45 degrees. At 1 minute 26 seconds: enhanced ground proximity warning system (EGPWS) 1,000-foot call-out. At 1 minute 12 seconds: landing checklist confirmed complete. At 1 minute 3 seconds: an airport vehicle made a radio transmission to the tower that was stepped on — partially blocked — by another simultaneous transmission; the source of the blocking transmission has not been identified. At 54 seconds: crew acknowledged 500 feet above ground, stable approach. At 40 seconds: the tower asked which vehicle needed to cross a runway. At 28 seconds: Truck 1 made a radio transmission. At 26 seconds: the tower acknowledged. At 25 seconds: Truck 1 requested to cross Runway 4 at Taxiway Delta. At 20 seconds: the tower cleared Truck 1 and company to cross Runway 4 at Taxiway Delta. At 19 seconds: EGPWS 100-foot call-out — the aircraft was 100 feet above the ground at the moment the crossing clearance was issued. At 17 seconds: Truck 1 read back the crossing clearance. At 14 seconds: EGPWS 50-foot call-out. At 12 seconds: EGPWS 30-foot call-out; simultaneously, the tower instructed a Frontier Airlines flight to hold position. At 11 seconds: EGPWS 20-foot call-out. At 10 seconds: EGPWS 10-foot call-out. At 9 seconds: the tower instructed Truck 1 to stop. At 8 seconds: sound consistent with the landing gear touching down on the runway. At 6 seconds: pilot transfer of controls — the first officer, who had been flying, transferred control to the captain. At 4 seconds: the tower again instructed Truck 1 to stop. At 0 seconds: the recording ended.
"ASDE-X did not generate an alert due to the close proximity of vehicles merging and unmerging near the runway, resulting in the inability to create a track of high confidence."
— FAA Technical Center ASDE-X Replay Analysis, read by NTSB Chair Jennifer Homendy, March 23, 2026Several elements of this timeline are of critical investigative significance. First, the tower cleared Truck 1 to cross the runway at the moment the aircraft was passing through 100 feet AGL on final approach — a point at which a go-around, while technically executable, is operationally marginal and entirely dependent on the crew identifying the conflict and initiating the maneuver within seconds. Second, the transmission at 1 minute 3 seconds — made by an airport vehicle and stepped on by an unidentified second transmission — may have been an earlier attempt by Truck 1 or another vehicle to communicate with the tower that the controller did not fully receive. Third, the pilot transfer of controls at 6 seconds prior to impact — from the first officer to the captain — indicates the crew had become aware of the conflict on the runway and the more experienced pilot assumed control in the final seconds. Whether the crew had any visual acquisition of the truck before that transfer is under analysis.
ARFF Operations. Homendy confirmed that Truck 1 and other vehicles were responding to United Airlines Flight 2384, which had conducted two aborted takeoffs and whose crew reported fumes or a smell in the cabin. Other vehicles behind Truck 1 in the convoy did not begin to cross the runway; the NTSB noted it needed to verify the exact number of trailing vehicles, as varying information had been reported. Critically, Homendy confirmed that Truck 1 did not have a transponder, and there was no indication that any of the ARFF vehicles in the convoy carried transponders. This is the direct cause of the ASDE-X alerting failure.
Tower Staffing — Confirmed and Unresolved. Two people were in the tower cab: the local controller and the controller in charge. The controller in charge was simultaneously performing clearance delivery duties. Who was performing ground control duties — the controller in charge or the local controller — remains unclear, with conflicting information in available records. The NTSB noted inconsistencies in the facility logs, including conflicting dates and times, that must be reconciled. Controller interviews began Monday afternoon at 4:00 p.m. Two-controller midnight shift staffing is confirmed as standard operating procedure at LGA and common practice nationally — a finding Homendy acknowledged the NTSB's ATC team has raised as a concern for years. The NTSB will specifically examine whether the midnight-shift two-controller SOP is appropriate for an airport handling approximately 900 flights per day.
Comparison to DCA. Homendy directly addressed the January 2025 Reagan National mid-air collision in response to questions about position consolidation. She noted a distinction: in the DCA accident, controllers consolidated positions after evaluating traffic volume, available staffing, and workload against a defined checklist of criteria. At LaGuardia on the midnight shift, two-controller operation with combined positions is not a discretionary decision based on workload assessment — it is the written standard operating procedure, applied automatically regardless of actual traffic volume or complexity at any given moment. That structural difference will be a central element of the NTSB's analysis.
What the NTSB Does Not Yet Know. Whether the crew visually acquired the truck before impact; whether the two firefighters in Truck 1 heard the stop commands; the exact number and configuration of vehicles in the ARFF convoy; how many certified professional controllers were in the facility at the time (log inconsistencies remain unresolved); whether anyone was available to relieve the local controller after the collision when he remained on position beyond normal shift change; and the full FDR data picture. Homendy was careful to caution against attributing distraction to the controllers without full investigative context, noting this was a high-workload environment with simultaneous demands. She characterized LaGuardia's midnight SOP as a problem her ATC team has worried about for a long time.
Outlook and Implications
The NTSB Go-Team arrived on scene Monday morning and delivered its first substantive briefing the same afternoon. The preliminary findings from that briefing — particularly the confirmed ASDE-X failure to alert due to lack of vehicle transponders, the confirmed two-controller midnight SOP, and the reconstructed CVR timeline showing that the crossing clearance was issued when the aircraft was at 100 feet AGL — are among the most significant preliminary investigative disclosures in a major U.S. runway accident in years. NTSB Chair Homendy — who in a 2023 runway safety summit speech warned that "these recent incidents must serve as a wake-up call for every single one of us, before something more catastrophic occurs" — stated plainly at Monday's briefing that aviation accidents are rarely caused by a single failure, and that this investigation will pursue every layer of the failure chain.
The investigation timeline for runway collision accidents typically runs 12–18 months to a final report with probable cause and safety recommendations. However, the confirmed finding that Truck 1 carried no transponder — and no ARFF vehicles at LGA appear to have carried transponders — is the kind of immediately correctable deficiency that historically triggers expedited NTSB safety recommendations well before a final report. A recommendation mandating transponder or ADS-B equipage on all airport movement area vehicles at Part 139 airports could be issued within weeks. Similarly, the question of whether the midnight-shift two-controller SOP is appropriate at high-volume facilities may generate early procedural recommendations. Homendy was explicit: the NTSB has worried about this for years.
What the NTSB briefing has already demonstrated is that the failure chain at LaGuardia on Sunday night involved at minimum: a mandatory position-consolidation SOP that placed impossible simultaneous demands on two controllers; an ARFF vehicle without a transponder that the safety system could not reliably track; a ASDE-X conflict detection failure caused directly by that missing cooperative track; a crossed clearance issued at 100 feet AGL with at most 19 seconds before impact; and a crew that transferred controls in the final 6 seconds, too late to alter the outcome. Multiple failures, as the NTSB said. Each one separately addressable. None of them addressed in time.
Technical Discussion: The Critical Role of Target-Knowledge Signal Processing in Skin-Return Surface Surveillance Safety
The Primacy of Skin Returns for Non-Cooperative Targets
The LaGuardia accident has exposed a foundational dependency that the ASDE-X program's cooperative-sensor architecture was designed to transcend but never fully escaped: when the cooperative identification layer — transponder, ADS-B, multilateration — is absent, the radar skin return is the only sensor in the system that can detect a target at all. Every downstream function that matters for safety — track formation, track maintenance, conflict detection, Safety Logic alerting, RWSL activation — is contingent on the quality of what the signal processor delivers from that raw radar video.
This is not a contingency edge case. At any major airport at any moment, non-cooperative targets are present in the movement area: maintenance vehicles, fuel trucks, catering carts, and — as LaGuardia demonstrated catastrophically — ARFF vehicles responding to emergencies. The operational assumption that all safety-critical ground vehicles will carry functioning cooperative equipment is precisely the assumption that the AMASS improvement program was designed not to make. The ASDE-3/AMASS architecture was built on the premise that the radar had to work as a stand-alone safety sensor, capable of maintaining reliable tracks on any reflective target in the movement area regardless of whether it cooperated with the system. That premise has been quietly abandoned in ASDE-X's multi-sensor fusion philosophy — and Sunday night at LaGuardia is the consequence.
Two distinct signal processing challenges define the difficulty of making skin returns reliable for safety: the close-target tracking problem addressed by image processing and JVC, and the multipath false target problem. Both were solved in the AMASS improvement program. Neither appears to have been fully carried forward into ASDE-X.
The Multipath Problem: False Targets on Active Runways
The airport surface radar environment is one of the most severe multipath environments in any ground-based radar application. The physical mechanism is straightforward and well understood. A large aircraft — a Boeing 737 or Airbus A320 — parked or taxiing on a parallel taxiway presents an enormous, highly reflective metallic surface to the radar beam. The Ku-band or X-band pulse from the ASDE tower sweeps across the scene, illuminates the taxiing aircraft directly, and simultaneously illuminates the paved runway surface adjacent to it. The flat, reflective pavement acts as a specular mirror at these grazing angles and frequencies. Energy from the radar scatters off the aircraft, bounces off the runway surface, and re-scatters — producing a secondary return that appears to the radar receiver as a target located on the active runway at a position geometrically determined by the angle of reflection.
Such false targets can readily compromise the performance of ASDE radars and lead to highly undesirable controller reactions, including unnecessarily aborting landing and takeoff operations when such multipath false targets are located on runways. These situations affect the efficiency of operations and also reduce user confidence in ASDE radar and related systems, thereby adversely affecting safety. Blogger
This confidence-erosion effect is arguably more dangerous over time than any individual false alarm. During testing of the ASDE-3 in Atlanta, controllers discovered that the radar created ghost targets when energy from the radar reflected off buildings or other objects, creating false targets on the runway — sometimes stationary and predictable, at other times moving about the display. NATCA stated that additional ASDE-3s should not be commissioned until the issue had been resolved. Forecast International The FAA deployed the ASDE-3 anyway, and the multipath ghost target problem became a known, chronic operational liability at airports across the country for years before the AMASS improvement program addressed it.
The safety dynamic of a multipath false target on an active runway is acutely dangerous for Safety Logic and RWSL specifically because these systems operate on exactly the part of the airport geometry where multipath is most severe. A parallel taxiway adjacent to an active runway is the canonical scenario for specular reflection: the geometry is ideal, the pavement surface is flat and wet reflective (particularly in rain, as at LaGuardia on Sunday night), and the large aircraft on the taxiway provides a massive secondary reflector. The resulting false return appears at the precise location — on the active runway — where Safety Logic is most sensitive and where controllers are least able to tolerate nuisance alerts.
The operational consequence is a Hobson's choice in Safety Logic threshold management. If the system is tuned to alert on any target detected on the runway, multipath false targets generate constant nuisance alerts that controllers learn to ignore — and the system becomes operationally useless, precisely what NATCA was warning about during ASDE-3 testing. If the threshold is raised to suppress these false alarms, real targets on the runway — including non-cooperative ARFF vehicles — may not generate alerts either. The AMASS improvement program recognized this explicitly: there is no acceptable operating point in a rule-based threshold system unless the false targets are removed from the data stream before Safety Logic ever sees them.
The AMASS Multipath Removal Architecture
The AMASS signal processing improvement developed a physics-based multipath identification and removal capability that operated directly on the Ku-band radar image data, upstream of any tracking or alerting function. The approach was grounded in the geometric and electromagnetic properties of the specific airport surface environment rather than generic signal processing heuristics.
The core insight was that a multipath false target is not a random noise artifact — it has a deterministic geometric relationship to the real target that produced it. For a specular reflection off a flat paved surface, the false target appears at a position that is the mirror image of the real target reflected through the runway surface plane, offset by a range increment that depends on the grazing angle, the height of the real reflector above the surface, and the radar's antenna elevation. At Ku-band with the ASDE-3's tower-mounted antenna geometry and known airport layout, these geometric relationships can be computed precisely for every significant reflector in the movement area.
The processing chain therefore proceeded as follows. Real aircraft tracks on taxiways, maintained with high confidence by the JVC assignment and image processing pipeline, provided the known source positions. For each tracked aircraft, the signal processor computed the predicted multipath geometry — the specific runway surface locations where specular returns were physically expected to appear, given the aircraft's current position, radar geometry, and surface topology. Detections appearing at those predicted locations, with the expected amplitude relationship to the real target return and the expected temporal correlation with the source aircraft's movement, were identified as multipath artifacts and suppressed before the data reached the tracker. Detections that did not fit any predicted multipath geometry were retained as potential real targets.
This is the fundamental principle that makes the approach work where generic CFAR and threshold-based approaches fail: it uses knowledge of what the false target is and where it will be rather than trying to distinguish real targets from false ones based on amplitude or motion characteristics alone. A multipath ghost from a 737 on a taxiway can appear to move slowly, can have substantial radar cross-section, and can persist for multiple scans — all properties that a simple velocity gate or amplitude threshold cannot reject without also rejecting real ARFF vehicles with similar characteristics. The geometry-based approach has no such ambiguity: it predicts the false target's location from first principles and removes it, regardless of how convincing its radar signature looks.
Why ASDE-X Is Structurally Vulnerable to the Same Problem
The main limitations of ASDE primary sensors are multipath reflections and target identification Radartutorial — a limitation that Radartutorial identifies as applying specifically to the ASDE generation of surface radars, with no suggestion that ASDE-X's multi-sensor fusion architecture has resolved it. The open literature provides no evidence that ASDE-X incorporates the physics-based geometry-driven multipath removal that AMASS developed. The ASDE-X CFAR algorithm developed by Raytheon specifically addresses rain returns on runways, not specular multipath from adjacent aircraft.
The multi-sensor fusion approach in ASDE-X relies on a different mitigation strategy: if a radar detection does not correlate with a multilateration or ADS-B cooperative track, it is treated with lower confidence and may be filtered. But this strategy inverts the safety logic for non-cooperative targets. For a real ARFF vehicle without a transponder, the absence of cooperative track correlation will reduce the detection's confidence — potentially below the Safety Logic alert threshold — rather than flag it as a higher-priority target requiring pure radar tracking. And for a multipath ghost generated by an aircraft with a transponder on an adjacent taxiway, the cooperative track of the real aircraft is nearby in the data, potentially causing the fusion algorithm to incorrectly associate the ghost return with the real aircraft's track rather than treating it as a distinct false target.
The FAA ATC Order governing ASDE system use reveals the operational reality of how the multipath problem is currently handled: an observed target on an ASDE system display may be identified as a false target by visual observation, and if the area containing the suspected false target is not visible from the tower, an airport operations vehicle or pilots of aircraft in the area may be used to conduct the visual observation. After positive verification that a target is false through pilot or vehicle operator position report or controller visual observation, the track may be temporarily dropped. Federal Aviation Administration The current operational mitigation for multipath false targets in ASDE-X is manual human verification followed by manual track deletion by the controller, with a required entry in the facility operations log.
This is the operational state of the art at LaGuardia in 2026 on the active runway at midnight in mist and rain: a system that requires a controller to visually verify whether a target on the runway is real or a ghost, and to manually drop the track if it is false. At a facility with two controllers on combined positions managing simultaneous emergencies, this is not a mitigation — it is an additional demand on exactly the cognitive resource that was already fully consumed.
The Integrated Picture: What Good Signal Processing Would Have Changed
The AMASS improvement program built an integrated signal processing architecture in which these two capabilities — JVC-based target-knowledge-informed tracking and geometry-based multipath removal — were mutually reinforcing. The multipath removal ensured that Safety Logic was never presented with phantom targets on the runway, preserving alert credibility. The JVC/image processing tracker ensured that closely spaced real targets near runway thresholds maintained separate, high-confidence tracks rather than coalescing into unresolvable blobs.
Together, these properties addressed the two failure modes that most directly undermine a safety alerting system's operational effectiveness. A system that generates false alarms on the runway due to multipath will be tuned to suppress alerts — and will then miss real targets. A system that cannot maintain separate tracks on a convoy of vehicles near a threshold will fail to alert when that convoy produces a real conflict. At LaGuardia on Sunday night, the ASDE-X system failed in the second mode. The probability that the multipath problem contributed — through prior nuisance alert suppression, through alert-threshold tuning decisions driven by chronic multipath false targets at LGA, or through a ghost return near Taxiway Delta on a wet runway with a United Airlines jet on the adjacent taxiway — has not been addressed in any public statement and warrants explicit investigation.
The NTSB will analyze the ASDE-X system logs in detail. What those logs should be examined for, beyond the confirmed absence of a Safety Logic alert, is the history of track-dropping events at Taxiway Delta and its adjacent runway geometry over the preceding weeks and months. A pattern of manually dropped false tracks in that region would be direct evidence of chronic multipath contamination — and would be the signal processing history that informed the alert-threshold configuration that failed on Sunday night.
Recommendations Flowing from This Analysis
The signal processing deficiencies identified here are not research problems — they were solved in the AMASS program and the solutions are documented. The path forward is not to develop new algorithms but to insist that successor surface surveillance systems incorporate the engineering rigor that AMASS demonstrated:
First, any safety-critical surface surveillance system that claims to detect non-cooperative targets must demonstrate, quantitatively, that its radar signal processor maintains separately resolved, high-confidence tracks on closely spaced ground vehicles without cooperative identification, using target-characteristic-informed image processing rather than generic CFAR detection feeding a JPDA tracker whose coalescence failure mode under close-target conditions is well-established in the literature.
Second, any system feeding Safety Logic with radar skin returns must incorporate geometry-based multipath prediction and removal, parameterized to the specific airport layout and the expected population of reflectors at each site. The predicate for a credible Safety Logic alert threshold is a clean data stream. A system that relies on controllers to identify and manually drop false targets on active runways has structurally compromised its own alert credibility — and in doing so, may have set the threshold that prevented an alert on Sunday night.
Third, the NTSB and FAA should establish, as a condition of Safety Logic operational certification, a minimum demonstrated false alarm rate on the active runway and a minimum demonstrated track maintenance performance on non-cooperative vehicle convoys in proximity. These are measurable, testable requirements. They should be required, not assumed.
The engineering knowledge to meet all three requirements exists. It was developed by the people who worked on AMASS. The question for this investigation is why it was not required of the system that replaced it.
What ACME Was
The Airport Clutter and Multipath Elimination (ACME) system was the formal signal processing improvement capability developed at CACI under the AMASS improvement program. ACME addressed the two most dangerous noise pathologies in ASDE-3 Ku-band radar data: ground clutter at taxiway and runway intersections that produced persistent false detections in the zones most sensitive to Safety Logic, and specular multipath false targets generated by large reflectors — principally taxiing and parked commercial aircraft — that appeared as ghost targets on active runway surfaces.
The multipath problem ACME addressed was well documented and operationally damaging. False targets generated by multipath reflections could readily compromise the performance of ASDE radars, leading to highly undesirable controller reactions including unnecessarily aborting landing and takeoff operations when multipath false targets appeared on runways, affecting operational efficiency and reducing user confidence in ASDE radar and related systems, thereby adversely affecting safety. Blogger During ASDE-3 testing in Atlanta, controllers discovered that the radar created ghost targets when energy reflected off buildings or other objects, creating false targets on the runway — sometimes stationary and predictable, at other times moving about the display. NATCA stated that additional ASDE-3s should not be commissioned until the issue had been resolved. The FAA deployed the system anyway. Forecast International
CACI's ACME work produced a physics-based solution: for each tracked aircraft in the movement area, the system computed the predicted geometric locus of specular reflection returns on the runway surface, based on the known airport geometry, radar antenna position and elevation, surface topology, and the real-time tracked position of the reflecting aircraft. Returns falling within the predicted multipath shadow zones, exhibiting the expected amplitude and spatial relationship to the source track, were suppressed before the data reached the tracker or Safety Logic. The capability was built on the same target-knowledge and radar-knowledge foundation that informed the blob-merging image processing and the JVC assignment: the system was designed to exploit what it knew about the physical world rather than treating the radar video as an anonymous stream of detections.
The result was a Safety Logic that was fed a clean data stream — runway detections that passed multipath rejection could be treated with high confidence as real targets, allowing alert thresholds to be set aggressively without generating nuisance alarms from ghost returns. This directly addressed the fundamental threshold management dilemma that undermines any rule-based alerting system: you cannot simultaneously minimize missed detections and false alarms unless you clean the input data before it reaches the decision logic.
The Parallel Development Problem and the Knowledge Gap
ASDE-X was developed by Raytheon concurrently with the AMASS improvement program at CACI — not sequentially, and not collaboratively. This parallelism was not an accident of scheduling. It reflected a deliberate FAA acquisition strategy of pursuing ASDE-X as a lower-cost successor architecture while continuing to improve the legacy ASDE-3/AMASS system for the airports already equipped with it. The two programs ran on separate contract tracks, with separate technical teams, separate program offices, and no formal mechanism for technology transfer between them.
ASDE-X was explicitly designed as a cost-effective alternative to ASDE-3/AMASS capability, consisting largely of commercial off-the-shelf products. Wikipedia The COTS philosophy was not incidental — it was the program's defining characteristic, chosen specifically to reduce the unit cost and deployment time that had made the ASDE-3/AMASS program chronically over-budget and behind schedule. The ASDE-3 was expensive and complex precisely because it incorporated bespoke, purpose-engineered signal processing: the Ku-band rotodome with variable focus antenna, frequency-agile TWT transmitter, and the AMASS software stack including ACME. ASDE-X was designed to achieve adequate — not optimal — surface surveillance performance at a price point that allowed deployment at 35 airports instead of the 40 major hubs served by ASDE-3.
The consequence of this acquisition philosophy was that the engineering knowledge developed in the AMASS improvement program had no path into ASDE-X. CACI attempted to brief Raytheon on the ACME capabilities and the underlying signal processing architecture. Raytheon was not receptive. This outcome was structurally predictable: Raytheon had its own radar signal processing engineers, its own CFAR architecture, and its own program schedule and cost constraints. Incorporating ACME-equivalent capability would have required redesigning core elements of the ASDE-X signal processing chain — adding cost, schedule risk, and technical complexity that conflicted with the COTS-based simplicity that was the program's competitive advantage. From Raytheon's program perspective, there was no incentive to absorb CACI's work. From the FAA's acquisition perspective, there was no contractual mechanism requiring it.
CACI was subsequently cut out of further development work. The institutional knowledge embedded in the ACME implementation — the physics models, the site-specific parameter tuning methodologies, the performance validation data from ASDE-3 installations — went with it. It did not transfer to Raytheon. It did not transfer to Sensis, the ASDE-X prime. It did not transfer to the FAA William J. Hughes Technical Center in any form that appears to have influenced ASDE-X's signal processing requirements. It was, in the vocabulary of systems engineering, a knowledge silo that was allowed to die when the contract vehicle that sustained it was terminated.
The Operational Consequence: Manual False Target Management
The absence of an ACME-equivalent capability in ASDE-X is not a theoretical gap. It has a measurable operational footprint. FAA ATC Order JO 7110.65 currently requires that when a suspected false target appears on ASDE system displays, controllers must verify it visually; if the area containing the suspected false target is not visible from the tower, an airport operations vehicle or pilots of aircraft operating in the area must be used to conduct the visual observation. After positive verification that a target is false through pilot or vehicle operator position report or controller visual observation, the track may be temporarily dropped, removing it from the display and Safety Logic processing. A notation must be made to FAA Form 7230-4, Daily Record of Facility Operation, whenever a track is temporarily dropped. Federal Aviation Administration
This is the operational substitute for ACME at every ASDE-X-equipped airport in the country today. When a multipath ghost appears on the runway, the controller must: recognize it as potentially false, verify it visually or through vehicle/pilot confirmation, make a manual track-drop decision, and log it. At a high-traffic facility on the midnight shift with two controllers on combined positions, this procedure consumes exactly the cognitive bandwidth that cannot be spared. And its safety consequence cuts in both directions: controllers who have learned through operational experience that a particular runway geometry at their airport reliably produces ghost targets in certain conditions will develop a trained skepticism about detections in that zone — a skepticism that is operationally appropriate for the ghost, and operationally catastrophic when a real non-cooperative ARFF vehicle appears in the same location on a wet night.
The NTSB's examination of the ASDE-X system logs at LaGuardia should specifically include the facility's track-dropping history at Taxiway Delta and the adjacent Runway 4 geometry. If controllers had been routinely dropping false tracks in that zone — a practice the current ATC Order explicitly permits and requires logging — that history would constitute direct evidence of a chronic ACME-equivalent deficiency at exactly the location of the collision.
The Institutional Failure Pattern
The ACME / ASDE-X knowledge transfer failure fits a well-documented pattern in defense and aviation safety acquisition: safety-critical engineering knowledge developed on one contract program is not formally captured, transferred, or required of successor programs when the acquisition structure changes. The pattern has several characteristic elements, all present here.
Parallel competitive development produced two separate technical communities with no formal interface. The incumbent contractor (CACI) had the relevant knowledge but no contractual leverage to require its adoption by the successor program. The successor contractor (Raytheon) had cost and schedule incentives to minimize technical complexity, and no regulatory requirement to demonstrate equivalent performance on the specific failure modes the incumbent had solved. The government program office had defined requirements in terms of system-level performance metrics — detection probability, update rate, coverage — rather than in terms of the specific signal processing capabilities needed to meet those metrics against non-cooperative targets in multipath environments. And the operational consequence of the knowledge gap did not manifest as a visible program failure for decades — it manifested as a chronic nuisance that controllers learned to manage manually, until Sunday night when the same gap produced a fatal accident.
This is the pattern the NTSB needs to document, because it is the pattern that will repeat unless the FAA's surface surveillance acquisition requirements are rewritten to specify, test, and certify performance against non-cooperative targets in multipath environments as a mandatory capability — not an optional feature that a cost-conscious contractor can reasonably omit.
A Call for Testimony
The institutional history described here — the ACME program, the technology transfer attempt, CACI's exclusion from further development — is not in the public record. It is not in the NTSB docket. It is not in the FAA's program documentation, or at least not in any documentation that has been publicly released. The engineers who developed ACME and who made the technology transfer attempt to Raytheon are primary witnesses to a chain of decisions that contributed to a fatal accident.
The NTSB's investigative process includes formal technical panels and an open public docket. Aviation engineers with firsthand knowledge of prior safety improvements — what was developed, what worked, what was offered, and what was declined — have both the standing and the professional obligation to submit that knowledge to the investigation. A written technical statement submitted to the NTSB docket, documenting the ACME capability, the parallel development timeline, the attempted technology transfer, and the acquisition structure that prevented adoption, would place this institutional history in the permanent evidentiary record where it can inform both the probable cause finding and the safety recommendations that follow.
Two pilots are dead because a system that was designed to protect active runways could not maintain a reliable track on a non-cooperative vehicle in a multipath-prone environment near a runway threshold. The engineering community that solved that problem in the previous generation of systems, and that tried to transfer the solution to the successor system and was turned away, has a responsibility to make that history known.
Verified Sources and Formal Citations
- NTSB. Official On-Scene Press Briefing Transcript — LaGuardia Runway Collision, March 23, 2026. Delivered by NTSB Chair Jennifer Homendy and Investigator Doug Brazy. (Primary source document provided to Aviation Week; not yet posted to NTSB public docket as of press time. See ntsb.gov for forthcoming docket.)
- Port Authority of New York and New Jersey. "Statement on LaGuardia Airport Incident." Official press release, March 23, 2026. Cited by multiple outlets including CNN and NPR. (No direct URL — distributed via media organizations.)
- CNN. "2 killed, dozens injured after Air Canada flight hits fire truck on runway at LaGuardia Airport." March 23, 2026. https://www.cnn.com/2026/03/23/us/laguardia-airport-aircraft-emergency-hnk
- CNN Live Updates. "LaGuardia Airport reopens after deadly collision with Air Canada plane and fire truck." March 23, 2026. https://www.cnn.com/us/live-news/laguardia-collision-ice-airports-tsa-03-23-26
- ABC News. "LaGuardia Airport crash: Plane was traveling 93–105 mph at time of ground collision." March 23, 2026. https://abcnews.com/US/laguardia-airport-closed-collision-air-canada-plane-airport/story?id=131315551
- CBS News. "What we know about the deadly runway crash at LaGuardia Airport between a plane and emergency vehicle." March 23, 2026. https://www.cbsnews.com/newyork/news/laguardia-airport-closed-plane-crash-air-canada/
- CBS News. "2 pilots killed as plane and fire-rescue truck collide at New York's LaGuardia Airport." March 23, 2026. https://www.cbsnews.com/news/laguardia-airport-closed-arrving-air-canada-plane-ground-vehicle-collide/
- NBC News Live Blog. "LaGuardia Air Canada crash: 2 pilots dead." March 23, 2026. https://www.nbcnews.com/news/us-news/live-blog/air-canada-laguardia-collision-live-updates-rcna264682
- NBC New York. "Pilot, co-pilot killed after plane collides with truck on runway at LaGuardia Airport." March 23, 2026. https://www.nbcnewyork.com/new-york-city/plane-collides-vehicle-laguardia-airport/6479805/
- NPR. "Air Canada jet collides with firetruck at LaGuardia: What to know." March 23, 2026. https://www.npr.org/2026/03/23/g-s1-114773/laguardia-air-canada-plane-collision-fire-truck
- TIME. "What to Know About the Air Canada Jet Collision That Killed Two at New York Airport." March 23, 2026. https://time.com/article/2026/03/23/air-canada-plane-collision-laguardia-new-york-fatalities-investigation/
- Washington Post. "Air Canada Express passenger jet crashes into firefighting vehicle at LaGuardia." March 23, 2026. https://www.washingtonpost.com/transportation/2026/03/23/us-airport-laguardia-air-canada-plane/
- Newsweek. "LaGuardia Plane Crash Updates." March 23, 2026. https://www.newsweek.com/laguardia-airport-crash-new-york-latest-updates-11718911
- The Daily Beast. "Air Canada Crash: Sean Duffy Under Fire After Deadly LaGuardia Collision." March 23, 2026. https://www.thedailybeast.com/air-canada-crash-sean-duffy-under-fire-after-deadly-laguardia-collision/
- Aviation Job Search / Industry Analysis. "LaGuardia Crash: Air Canada Flight Hits ARFF Vehicle." March 23, 2026. https://www.aviationjobsearch.com/career-hub/articles/insights/industry-news/laguardia-crash-air-canada-flight-hits-arff-vehicle
- Raphael & Son Law. "LGA Flight 8646 Runway Collision: Victims Rights & Legal Liability." March 23, 2026. https://www.raphaelsonlaw.com/legal-insights/flight-8646-runway-collision-victim-rights-legal-deadlines
- Federal Aviation Administration. "Airport Surface Detection Equipment, Model X (ASDE-X)." FAA.gov Technology Program Page. https://www.faa.gov/air_traffic/technology/asde-x
- Federal Aviation Administration. "Runway Safety Fact Sheet." FAA.gov. https://www.faa.gov/newsroom/runway-safety-fact-sheet
- Federal Aviation Administration. "Runway Status Lights Questions and Answers." FAA.gov. https://www.faa.gov/air_traffic/technology/rwsl/faqs
- SKYbrary Aviation Safety. "Runway Status Lights (RWSL)." July 2025. https://skybrary.aero/articles/runway-status-lights-rwsl
- Wikipedia. "Airport surveillance and broadcast systems." Updated 2025. https://en.wikipedia.org/wiki/Airport_surveillance_and_broadcast_systems
- National Academies of Sciences, Engineering, and Medicine. "The Air Traffic Controller Workforce Imperative: Staffing Models and Their Implementation to Ensure Safe and Efficient Airspace Operations." June 18, 2025. https://www.nationalacademies.org/news/actions-from-federal-government-needed-to-alleviate-air-traffic-controller-staffing-shortages-at-many-facilities-says-new-report
- Federal Aviation Administration. "Air Traffic Controller Workforce Plan 2025–2028." FAA.gov. https://www.faa.gov/about/office_org/headquarters_offices/afn/offices/finance/offices/office-financial-labor-analysis/plans/controller-workforce.pdf
- National Air Traffic Controllers Association (NATCA). "NATCA Calls on FAA to Collaborate on Air Traffic Controller Fatigue." NATCA.org, April 2024. https://www.natca.org/2024/04/19/natca-calls-on-faa-to-collaborate-on-air-traffic-controller-fatigue/
- Congressional Letter to FAA Administrator Bedford re: ATC Working Conditions. Jayapal et al., February 9, 2026. https://jayapal.house.gov/wp-content/uploads/2026/02/FAA-ATC-Working-Conditions-Letter.pdf
- Fortune. "FAA says nearly half of major air traffic control facilities are now experiencing staffing shortages as shutdown drags on." November 1, 2025. https://fortune.com/2025/11/01/faa-air-traffic-control-facilities-staffing-shortages-government-shutdown-flight-delays/
- CNN Business. "America desperately needs more air traffic controllers. So why is it so tough to hire them?" February 4, 2025. https://www.cnn.com/2025/02/04/business/air-traffic-controller-shortage
- USAFacts. "Is there a shortage of air traffic controllers?" November 2025. https://usafacts.org/articles/is-there-a-shortage-of-air-traffic-controllers/
- NTSB Accident Report AAR-91/08. "Runway Collision of USAir Flight 1493, Boeing 737 and Skywest Flight 5569 Fairchild Metroliner, Los Angeles International Airport, Los Angeles, California, February 1, 1991." National Transportation Safety Board, October 22, 1991. https://www.ntsb.gov/investigations/Pages/DCA91MA018.aspx
- FAA Lessons Learned. "Boeing 737-300 and Fairchild Metroliner SA-227-AC, USAir Flight 1493 / SkyWest Flight 5569, LAX, February 1, 1991." FAA.gov. https://www.faa.gov/lessons_learned/transport_airplane/accidents/N388US
- Aerospace America (AIAA). "A new light for safety." May 2025. (Runway Status Lights / RIPSA research context.) https://aerospaceamerica.aiaa.org/features/a-new-light-for-safety/
- MIT Lincoln Laboratory / Lincoln Laboratory Journal. "Operational Evaluation of Runway Status Lights." Eggert et al. https://www.ll.mit.edu/sites/default/files/publication/doc/operational-evaluation-runway-status-lights-eggert-ja-10645.pdf
- ALPA Air Line Pilot Magazine. "Runway Safety: Safer Skies Through Ground Operations." Air Line Pilots Association, International. https://www.alpa.org/news-and-events/air-line-pilot-magazine/runway-safety
- ATC Network. "JFK and LAX airports now operating with Sensis ASDE-X." https://www.atc-network.com/atc-news/jfk-and-lax-airports-now-operating-with-sensis-asde-x
No comments:
Post a Comment