Delta Plane Crash at Toronto Pearson Airport Leaves 18 Injured

Updated: Apr 14, 2026
Overview of the Incident
On February 17, 2025, a Bombardier CRJ-900 operating as Delta Air Lines flight DL4819 overturned during landing at Toronto Pearson International Airport in Toronto, Ontario. The Endeavor Air-operated regional jet had departed Minneapolis and was carrying 80 people, with public reporting placing the accident at about 2:15 p.m. local time. Federal investigators in Canada are examining the landing sequence with particular focus on touchdown stability, winter wind conditions, and the aircraft’s post-touchdown ground response.
Publicly reported accounts state that the aircraft flipped over during touchdown and came to rest inverted on the runway. Eighteen people were reported injured, including three initially described as critically injured, but no fatalities were reported. Emergency crews evacuated passengers from the aircraft, and airport operations were temporarily disrupted while response and investigative work began.
Weather was described in public reporting as winter operational weather, including blowing snow and wind gusts reportedly reaching 40 mph. Snow and ice were reported in the airport environment, although the airport fire chief publicly described the runway as dry. Canada’s Transportation Safety Board said it recovered both the cockpit voice recorder and flight data recorder, while public reporting also mentioned a possible flap actuator issue and a hard landing, neither of which had been established as the cause in the reporting available at that stage.
Landing Stability and Post-Touchdown Ground Dynamics in Gusting Winter Conditions
The defining feature of this occurrence is that the aircraft overturned at touchdown rather than during a later runway excursion or post-landing fire sequence. That narrows the initial technical focus. Investigators will likely concentrate on the final approach, the flare, the first runway contact, and the aircraft’s motion in the first moments after touchdown.
That phase of flight leaves little margin for correction. By the time an aircraft crosses the threshold, speed, descent profile, alignment, and configuration should already be controlled within tight tolerances. A landing accident at the point of touchdown usually places immediate emphasis on whether the approach was stabilized, whether the flare and sink rate were managed properly, and how wind conditions affected the transition from flight to ground roll.
Public reporting does not provide the data needed to determine whether stabilized approach criteria were met. No published account in the source material identifies the aircraft’s crossing speed, descent rate, touchdown point, or lateral alignment at runway contact. Those are not minor omissions. They are core parameters investigators typically reconstruct from recorder data, cockpit communications, and air traffic control records.
Blowing snow and strong gusts can materially complicate the final segment of an approach even when the runway itself is later described as dry. Gusts can alter indicated airspeed and descent performance in seconds, which affects flare timing and increases the chance of a firm or uneven touchdown. Crosswind effects also become more consequential at the runway surface, where directional control demands can increase while aerodynamic control authority is changing with deceleration.
Winter visual conditions matter as well. A dry runway surface does not eliminate the operational significance of snow, drifting snow, or reduced contrast around the runway environment. That distinction matters because a crew’s height, alignment, and edge-definition cues during the flare can be affected by the broader visual scene, not only by whether liquid contamination is present on the pavement itself.
The fact that the aircraft came to rest inverted makes the ground-dynamics question especially important. Once the wheels are on the runway, the aircraft’s motion reflects a combination of tire-runway interaction, braking forces, residual lift, crosswind input, yaw development, and landing-gear loading. Public reporting does not identify whether the aircraft deviated laterally, whether one gear leg contacted abnormally, or whether any runway-edge, snowbank, or directional-control sequence contributed to the inversion. The absence of those details does not mean they are unimportant. It means they remain to be established through evidence rather than assumption.
Reports describing the event as a hard landing should be treated carefully. That phrase can describe a touchdown involving higher vertical loads, but by itself it does not explain why those loads developed or whether they were central to the aircraft overturning. Investigators will likely use recorded parameters to determine sink rate, flare timing, pitch attitude, touchdown loading, and whether the touchdown sequence included bounce, asymmetric loading, or other destabilizing features.
Some public reporting also referenced a flap actuator failure. That possibility is operationally significant because flap position directly affects approach speed, lift characteristics, drag profile, and landing handling. But the reporting available here does not identify the timing, nature, or confirmation status of any flap-related anomaly. That is an important limit. Until investigators validate a system issue, the safer reading is that configuration remains an investigative question rather than an established explanation.
This places the investigation on a broader systems track rather than a single-factor narrative. Investigators will likely examine approach stability, wind and visibility conditions, aircraft configuration, touchdown forces, landing gear response, and the aircraft’s immediate path after runway contact. The recovered cockpit voice recorder and flight data recorder should be central to that reconstruction. Those data will matter more than early descriptive labels.
Relevant Regulatory Framework
Because the accident occurred in Canada, the Transportation Safety Board of Canada is the authority responsible for the safety investigation and for issuing findings, safety communications, or recommendations if warranted. Public reporting indicated that the TSB recovered both the cockpit voice recorder and flight data recorder, which are standard and often decisive sources in reconstructing approach and landing events. That procedural point is significant because touchdown accidents often turn on timing, configuration, and control inputs that cannot be resolved reliably from witness accounts alone.
At the same time, the flight was operating in a U.S. commercial carrier context under the Delta brand through Endeavor Air. Public reporting in the source material does not identify the specific operating manuals, stabilized-approach criteria, winter-operations procedures, or training guidance applicable to this crew. For that reason, the regulatory discussion here remains necessarily general. The key issue is whether the aircraft was operated within the performance and procedural framework expected for a transport-category landing in gusting winter conditions, which is something investigators typically determine only after reviewing recorded data and operator documentation.
Focused Legal Dimension
From a legal perspective, a landing overturn event usually depends on the same factual record the safety investigation is still building: approach profile, configuration, touchdown loads, environmental conditions, crew actions, and any confirmed system anomaly. That overlap is important because early public descriptions often identify possible themes before the evidentiary sequence is actually established. At the stage reflected in the source material, no final investigative determination had been issued, so assigning fault would be premature.
If investigators ultimately confirm a flap-system problem or another aircraft-system issue, that would ordinarily direct attention to maintenance history, inspection records, prior discrepancy reporting, and manufacturer or operator guidance relevant to the confirmed condition. If the evidence instead centers on the conduct of the approach and landing, the analysis would more likely focus on stabilized approach compliance, operational decision-making, and touchdown control in adverse weather. Those are materially different legal pathways. The current public record does not justify choosing between them.
Preliminary Reports and Investigative Timeline
Public reporting stated that the TSB recovered both onboard recorders for analysis. In aviation investigations, that is an early but consequential step because recorder data can establish sequence, timing, configuration, airspeed trends, sink rate, and aircraft motion with far greater precision than initial eyewitness reporting. In a touchdown overturn event, those details are likely to frame the entire investigation.
Preliminary investigative materials generally identify the known facts about the aircraft, crew, environment, and event sequence without drawing a final conclusion on cause. A final report typically follows after additional work that may include interviews, maintenance and operational record review, airport condition documentation, performance analysis, and detailed examination of relevant structures or systems. That process takes time because investigators are not simply asking what happened. They are also determining how the sequence developed and whether any safety lessons should follow.
Until formal findings are issued, publicly reported references to a hard landing or a specific component issue should be understood as unverified early descriptions rather than established conclusions. That is not a technicality. It is the difference between an initial narrative and an evidence-based determination.
About This Analysis
This analysis is based exclusively on publicly reported information concerning the February 17, 2025 accident at Toronto Pearson International Airport. It does not add unreported facts, infer an unproven causal sequence, or assign responsibility before the investigative record is complete. Definitive conclusions depend on the formal findings of the Transportation Safety Board of Canada. Additional background on related commercial-air-carrier injury matters appears in the firm’s work as counsel for plane crash litigation.
Consultation Regarding Aviation Accident Investigations
Families, referring attorneys, and journalists sometimes seek legal consultation or technical insight regarding aviation accidents and investigative issues discussed in these analyses. Inquiries may be directed to Katzman, Lampert & Stoll at the link below.
Aviation Accident Litigation
- Aviation Accident Litigation
- Commercial Airline Accident Litigation
- Private & Corporate Aircraft Accident Litigation
- Military & Government Contractor Aviation Litigation
- Complex Aviation Litigation Methodology
- NTSB Investigations & Civil Aviation Claims
- Federal Preemption in Aviation Product Liability
- Defeating GARA Defenses in Aviation Product Liability Litigation
- For Families and Survivors
MICHIGAN OFFICE
Katzman Lampert & Stoll
950 West University Dr #101
Rochester, MI 48307
E-mail: Click to use our Contact Form
Toll-Free: (866) 309-6097
Phone: (248) 258-4800
Fax: (248) 258-2825
COLORADO OFFICE
Katzman Lampert & Stoll
9596 Metro Airport Ave.
Broomfield, CO 80021
E-mail: Click to use our Contact Form
Toll-Free: (866) 309-6097
Phone: (303) 465-3663
Fax: (303) 867-1565
PENNSYLVANIA OFFICE
Katzman Lampert & Stoll
121 N. Wayne Ave. # 205
Wayne, PA 19087
E-mail: Click to use our Contact Form
Toll-Free: (866) 309-6097
Phone: (610) 686-9686
Fax: (610) 686-9687
