What happened in the LaGuardia runway collision between an Air Canada jet and a fire truck?
The gist: A Jazz Aviation Bombardier CRJ 900, flying as Air Canada Express Flight 8646, collided with an aircraft rescue and firefighting vehicle while landing at LaGuardia Airport around 11:37 p.m. Eastern Daylight Time, with 72 passengers and four crew on board and two firefighters in the truck [1]. The NTSB has recovered the cockpit voice recorder and flight data recorder and, on its first full day on scene, laid out a preliminary timeline from the final three minutes of cockpit audio — one in which a fire truck was cleared to cross the landing runway while the airplane was on short final [2][3][4][5]. Investigators have stressed that the information is preliminary, that they are ruling nothing out, and that they do not yet know why the truck was on the runway or whether the crew saw it [6][7][8].
What's going on
The accident and the aircraft. NTSB Chairwoman Jennifer Homendy said the agency is investigating "a collision between a Bombardier CRJ 900 with an aircraft rescue and firefighting vehicle while the aircraft was landing at LaGuardia last night around 11.37 p.m. Eastern Daylight Time"[9] [1]. The airplane was operated by Jazz Aviation, doing business as Air Canada Express Flight 8646, and carried 72 passengers and four crew; two firefighters were in the firefighting vehicle [1]. Homendy expressed the board's condolences to those who lost loved ones and said five members of the agency's transportation disaster assistance team were on scene working with the American Red Cross [10][11].
The recorders. Investigator-in-charge Doug Brazy said the airplane carried "an Akron aviation model Survivor 2-5 cockpit voice recorder and an Akron aviation model FA-2100 flight data recorder"[6]. The CVR held more than 25 hours of good-quality audio across four channels, and the FDR about 80 hours of data across more than 400 parameters [6]. Because the tail of the aircraft was on the ground, the Port Authority and emergency responders cut a hole in the roof to retrieve the recorders, and an NTSB investigator drove them to the labs in Washington, D.C. [12]. The CVR was verified as undamaged [13]. The NTSB took possession at 9:57 a.m. Eastern [2].
The sequence from the cockpit voice recorder. Brazy presented a summary of the final three minutes, with all times referenced to the end of the recording [3]. Three minutes and seven seconds before the end, the approach controller instructed the airplane to contact LaGuardia tower; at 2:45 the crew lowered the landing gear; at 2:22 they checked in with the tower; and at 2:17 the tower cleared the airplane to land on runway four and advised it was number two for landing [3][14]. The crew set flaps to 30 degrees at 1:52 and to 45 degrees at 1:33, and an enhanced ground proximity warning system callout indicated 1,000 feet above ground at 1:26 [14]. The landing checklist was confirmed complete at 1:12 [15].
At 1:03, an airport vehicle made a radio transmission to the tower that "was stepped on by another radio transmission,"[15] and the source has yet to be identified. At 54 seconds the crew acknowledged 500 feet and a stable approach [15]. At 40 seconds the tower asked which vehicle needed to cross a runway; at 28 seconds truck one transmitted to the tower; at 26 seconds the tower acknowledged; at 25 seconds truck one requested to cross runway four at taxiway Delta; and at 20 seconds "the tower cleared truck one and company to cross runway four at taxiway Delta"[4].
Electronic callouts followed at 100, 50, 30, 20 and 10 — and at the 30 callout the tower also instructed a Frontier Airlines flight to hold position [5][16]. At nine seconds the tower instructed truck one to stop; at eight seconds there was "a sound consistent with the airplane's landing gear touching down on the runway"[16]; at six seconds there was a transfer of controls from one pilot to the other; and at four seconds the tower again instructed truck one to stop. The recording ended at zero [16]. Homendy clarified that the first officer was flying and transferred control to the captain [17].
The fire truck and the alert system. Truck one — the vehicle that collided with the aircraft — was responding to United Airlines flight 2384 at the gate, which had two aborted takeoffs and reports of fumes, smoke or some sort of smell in the cabin [17][18]. Other vehicles behind truck one did not begin to cross the runway, though Homendy said the number of vehicles still needs verification [18]. Truck one did not have a transponder, and "we have no indication there were transponders on any of the trucks"[19] at LaGuardia, though other airports' trucks do have them [18][20].
On LaGuardia's surface detection system, Homendy read the FAA tech center's analysis verbatim: "ASDX 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"[21] [22]. She said the replay showed two radar targets — "two blobs on taxiway Delta"[23] — and that none of them appeared to go in front of the plane on the runway; the runway status lights were functioning according to the replay, pending verification with FAA tech ops [22].
The tower. Homendy said there were two people in the tower cab at the time of the collision: the local controller and the controller in charge [24][25]. The local controller had signed in at 10:45 p.m. for a shift ending at 6:45 a.m., and the controller in charge signed in at 10:30 p.m. for a shift ending at 6:30 a.m. [25][26]. The controller in charge was also performing clearance delivery duties, and it is not clear who was conducting ground control duties — information conflicts on whether it was the controller in charge or the local controller [26][27]. Homendy said combining those positions is in LaGuardia's standard operating procedures for the midnight shift and is common practice nationally [27]. She noted the NTSB has raised fatigue concerns about midnight shifts in past investigations but said "we do have no indication that was a factor here"[28].
Why it matters
The board's framing is that this is unlikely to be a single-point failure. "We rarely, if ever, investigate a major accident where it was one failure,"[29] Homendy said, adding that the aviation system is safe "because there are multiple, multiple layers of defense built in to prevent an accident"[29] — and that when something goes wrong, "many, many things went wrong"[29]. The preliminary record already shows several layers that did not hold: a truck without a transponder, an alert system that did not alert, a radio transmission stepped on by another, and a tower combining positions on a midnight shift at an airport Homendy described as handling roughly 900 flights a day [18][21][15][27][30].
The surface-detection gap is central. Homendy said the NTSB has "repeatedly recommended that ASDX work,"[31] and that for it to work well "you have to know where ground vehicles and aircraft are"[31] — in this case the vehicle had no transponder, and a radar target does not give a controller the information an aircraft transponder would. She added that controllers "should have all the information and the tools to do their job,"[32] and that "this is 2026" while "we have an old air traffic control system"[32]. She was careful to say a transponder requirement is not an NTSB recommendation and that whether trucks should carry them is something the investigation will determine [33][34].
The staffing question carries its own weight. Homendy cautioned against pointing fingers at controllers over distraction, calling it "a heavy workload environment"[35] with the United flight in progress, and said the board still has to determine what happened at the shift change around 10:30 and who else was available. She noted the controller remained on duty for several minutes afterward when they would normally have been relieved, and that the board has questions about whether anyone was available to relieve them [35]. She also said the NTSB's air traffic control team has called the two-controller midnight staffing a problem and a concern "for years" [36], and that whether that setup makes sense at an airport as busy as LaGuardia will be part of the analysis [30][37].
What's still unclear
Much of the core sequence remains unverified. Homendy said there is no information at this time on whether the pilots saw the fire truck on the runway, and that further CVR analysis and a public transcript will follow [7]. The board does not know whether the two firefighters in the vehicle heard the directive to stop, and needs to interview them [38]. It has not determined whether the truck turned or braked, saying only that investigators have probably seen the same CCTV video as the press [39][38].
On the flight data recorder, the download had not yet been completed at the time of the second briefing; the group was beginning to go through "good data" [40]. The FDR and the ASDE analysis are expected to help establish where the aircraft was when the controller cleared the truck to cross [41].
Tower staffing records are contested. Homendy said the board has seen different information about how many certified professional controllers were in the facility, that logs contain conflicting dates and times, and that interviews with controllers were to begin that afternoon, starting with the local controller at 4 p.m. [24]. She declined to provide controller experience or pilot backgrounds pending verification against sign-in sheets, time cards, interviews and airline records [42][43]. She also said the board cannot yet answer whether the two controllers, each doing more than one job, could have had conflicting or overlapping communications — "that's something we have to investigate"[44].
Finally, the board declined to confirm fatalities, injuries or the names of the pilots, referring those questions to the New York City Chief Medical Examiner [39][45]. It also cautioned that ADS-B in and out may or may not have made a difference, because the collision "happened very quickly" and times, visibility and the movement of those in the truck still need to be matched up [46][19]. The Transport Safety Board of Canada will participate as the state of the operator under ICAO Annex 13, with technical advisors from the operator and likely the manufacturer [47][48].
Written with AI (Memex) from 48 cited source passages. Every quotation was checked word-for-word against the sources: 18 of 18 verified.