Two Killed in LaGuardia Crash; Controllers Left Early, FAA Investigating
A regional jet crash at LaGuardia Airport killed two crew members; the NTSB is investigating whether staffing played a role.
2 reports on this incident · first at Aug 27, 2026, 3:22 p.m. ET
Earlier reports
Aug 27, 2026, 3:22 p.m. ETFirst report
Two Controllers Left Early Before Fatal LaGuardia Crash, NTSB Probes Staffing Role
The NTSB is investigating a fatal crash at LaGuardia Airport on March 22, 2026, that killed two people, according to newser.com. The incident is still under investigation, and the NTSB has yet to conclude whether staffing issues played a role.
Two air-traffic controllers at LaGuardia left their shifts early before the crash, and the FAA is reportedly moving to fire them, newser.com reported. The NTSB is still investigating the incident but has not determined the cause.
The aircraft involved has not been identified. Registry records list Air Canada as operating 147 aircraft, but these records do not identify the specific aircraft involved in the incident.
Was this report accurate and useful?
Reference data
From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.
- Registration
- C-GNJZ
- Type
- Bombardier Inc. CL-600-2D24 (Series 900) (Bombardier) — twin-engine jet landplane
- Registered owner
- Jazz Aviation LpThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
- Terrain elevation
- 105 ft
- Nearest aerodrome
- 8.3 miles WSW of LaGuardia Airport (KLGA/LGA)
Sources
- Two Controllers Reportedly Left Early Before Fatal Crashnewser.com
- Air-traffic controllers left off work early before LGA crash, FAA saysdailymail.com
- Flight controllers allegedly punched out early before Air Canada plane crashtoronto.citynews.ca
- The FAA Is Firing 2 LaGuardia Controllers Who Clocked Out an Hour Early Before a Deadly Crash, Leaving the Tower Short-Staffed on Its Busiest Nightthoughtcatalog.com
Revision history
- Version 328 Aug 2026, 20:53current
Added 'the registered owner of record and not necessarily connected to the flight' after 'Jazz Aviation' to satisfy the owner_unframed warning.
- Version 228 Aug 2026, 19:53
Added identification of aircraft from NTSB case record; clarified conflicting reports on NTSB investigation status.
- Version 127 Aug 2026, 19:22current
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.