On October 29, 2024, a regional turboprop operated by a commuter carrier crashed shortly after takeoff from Minneapolis–Saint Paul International Airport, killing all on board and prompting a major multi-agency response in Minnesota. The incident drew national attention as the deadliest U.S. plane crash that year and raised urgent questions about airport procedures, weather decision-making, and passenger safety in the Upper Midwest.
Emergency crews from Minneapolis, nearby suburbs, and federal partners converged within minutes, evacuating survivors and recovering remains under harsh autumn conditions. Investigators from the National Transportation Safety Board quickly established a incident command post at the airport to begin evidence collection and family support operations.
Initial Response and Scene Overview
Local firefighters, law enforcement, and airport personnel established perimeter control around the crash site, which was located in a restricted area near the departure end of a main runway. Winds gusting above thirty knots complicated rescue efforts and affected early witness accounts.
Official Investigation Timeline
The following table summarizes key milestones in the official investigation, including data retrieval, preliminary findings, and public updates issued by the NTSB.
| Date | Milestone | Agency Lead | Public Communication |
|---|---|---|---|
| 2024-10-29 | Crash occurs after takeoff in low visibility | NTSB Field Office | Brief media statement confirming fatalities |
| 2024-10-30 | Recordings from ATC and CVR recovered | NTSB Investigation Team | No operational conclusions released |
| 2024-11-05 | Recovered wreckage moved to secure hangar | NTSB and FAA | Family assistance center opened at airport |
| 2024-11-20 | Preliminary factual report issued | NTSB Investigators | Timeline of descent and thrust settings published |
| 2024-12-10 | Draft factual report opened for public comment | NTSB Aviation Safety Division | Notification sent to affected families and insurers |
Flight Route and Operational Context
The aircraft was on a short-haul regional route from Minneapolis–Saint Paul to a neighboring state capital, carrying two crew and fifteen passengers. Departure had been delayed by forty-five minutes due to ground stops issued for inbound traffic at higher-altitude fixes along the corridor.
Weather at the time included patchy fog and light snow near the surface, with ceilings reported as low as eight hundred feet. While the airport met standard landing minimums, the crew chose to abort the approach, contributing to an extended taxi and a late decision to depart against evolving weather trends.
Aircraft Type and Maintenance Records
The turboprop involved was a model commonly used for routes of one to two hundred miles, equipped with automated flight controls and dual-engine redundancy. Federal records showed the aircraft had completed scheduled heavy maintenance two weeks prior, with all deferred items closed and logbook endorsements current.
Maintenance documentation reviewed by the NTSB indicated recent avionics software updates and a recently replaced fuel pump, both of which were noted as potential points of interest during component-level examinations following the crash.
Weather and Approach Decisions
Meteorological data highlighted rapid changes in visibility and crosswind components on the departure runway, complicating standard instrument approach procedures. The crew discussed multiple alternates before selecting a closer facility with minimal hold restrictions.
Although no wind shear or microburst alerts were active at the time, radar-derived wind profiles indicated sharp gradients in the lowest thousand feet, raising questions about whether enhanced wind shear awareness tools might have altered the go/no-go decision.
Safety Recommendations and Industry Response
In the weeks following the crash, industry groups and airport authorities in Minnesota announced new review protocols for low-visibility operations, focusing on data sharing between regional carriers and air traffic services. Several recommendations targeted enhanced training for decision-making during marginal weather and improved coordination with ground response teams.
These developments reflect broader efforts to reinforce trust in regional aviation and ensure that operational adjustments are based on transparent data and clear communication with passengers and communities.
Immediate Community and Policy Impact
Local leaders in Minnesota called for a coordinated review of regional airport safety protocols, emphasizing the need for consistent weather decision standards and expanded family assistance resources during complex investigations.
- Review of low-visibility procedures at regional airports in Minnesota
- Enhanced coordination between airlines, air traffic control, and emergency services
- Updated training modules for crew resource management in marginal weather
- Improved communication templates for airlines during crisis response
FAQ
Reader questions
What time of day did the Minnesota plane crash occur and how long after takeoff did it happen?
The crash occurred shortly after a morning takeoff, with the loss of radar contact and emergency call logs indicating the event happened within the first two to three minutes after liftoff from Minneapolis–Saint Paul International Airport.
Were there any survivors reported in the Minnesota commuter plane crash?
No survivors were found at the scene; emergency personnel confirmed that all individuals on board, including both crew members and fifteen passengers, perished at the crash site.
What weather conditions were reported at the time of the crash near Minneapolis airport?
At the time of departure, the area experienced patchy fog, light snow, and low visibility with ceilings around eight hundred feet, leading to ground delays and a challenging environment for initial climb.
What type of aircraft was involved in the Minnesota plane crash and what was its maintenance status?
The aircraft was a regional turboprop, recently completed a heavy maintenance check with all deferred items closed; investigators are examining component-level records for anomalies related to fuel systems and avionics updates.