AERO COMMANDER 500 B near Chicago, IL — 2014-11-18
- Date
- 2014-11-18
- Location
- Chicago, IL, USA
- Airport
- MDW
- Aircraft
- AERO COMMANDER 500 B
- Registration
- N30MB
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 1
- Phase of flight
- Initial climb
Probable cause
The pilot's failure to maintain airspeed while attempting to return to the airport after a reported engine problem, which resulted in an aerodynamic stall/spin.
NTSB narrative
The commercial pilot was conducting an on-demand cargo charter flight. Shortly after takeoff, the pilot informed the tower controller that he wanted to "come back and land" because he was "having trouble with the left engine." The pilot chose to fly a left traffic pattern and return for landing. No further transmissions were received from the pilot. The accident site was located about 0.50 mile southeast of the runway's displaced threshold. GPS data revealed that, after takeoff, the airplane entered a left turn to a southeasterly course and reached a maximum GPS altitude of 959 ft (about 342 ft above ground level [agl]). The airplane then entered another left turn that appeared to continue until the final data point. The altitude associated with the final data point was 890 ft (about 273 ft agl). The final GPS data point was located about 135 ft northeast of the accident site. Based on GPS data and the prevailing surface winds, the airspeed was about 45 knots during the turn. According to the airplane flight manual, the stall speed in level flight with the wing flaps extended was 59 knots. Postaccident examination and testing of the airframe, engines, and related components did not reveal any preimpact mechanical failures or malfunctions that would have precluded normal operation; therefore, the nature of any issue related to the left engine could not be determined. Based on the evidence, the pilot failed to maintain adequate airspeed while turning the airplane back toward the airport, which resulted in an aerodynamic stall/spin.
Analysis
- Primary failure mode
- Engine power loss
- First missed decision gate
- Pilot could have aborted takeoff after engine trouble was reported.
NTSB coding
Evidence available
- ATC audio
- ADS-B / radar
- Photos
- 28 docket documents
Docket documents28
- Transcript of Air Traffic Control Communicationsatc
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Statement of Fixed Base Operator Representativeinterview
- Statement of Party Representatives to NTSB Investigationinterview
- Airplane Flight Manual (Excerpt) - Stall Speed Chartother
- Central Air - Air Route Worksheetother
- Central Air - Aircraft Status Sheetother
- Central Air - Load Manifestother
- Central Air - Pilot Duty Recordother
- Central Air - Pilot Training Recordsother
- Conversation Summary - Pilot's Wifeother
- Electronic Devices - Tabular Data (CSV) - Garmin GPS 396other
- Electronic Devices - Tabular Data (CSV) - iPhoneother
- Flight Planother
- Fuel Servo Testing Worksheetother
- Maintenance Records - Airplane Inspection & Discrepancies (Excerpts)other
- Maintenance Records - Left Engine (Excerpts)other
- Maintenance Records - Left Propeller (Excerpts)other
- Maintenance Records - Right Engine (Excerpts)other
- Maintenance Records - Right Propeller (Excerpts)other
- Maintenance Records - Weight & Balanceother
- Plot of GPS Dataother
- Propeller Testing Documentationother
- Weather Data - MDWother
- Report Photosphotos
- Electronic Devices - Specialist's Factual Reportreport
- Propeller Governor CT Examination Reportreport
- Toxicological Reportreport
Related mishaps
- BEECH E90
2025-06-16 · New Century, KS
- BUCKEYE DREAM MACHINE
2024-10-27 · Nicholasville, KY · 2 fatalities
- LANCAIR ES
2024-07-22 · Oshkosh, WI · 2 fatalities
- CESSNA 421
2024-06-17 · Steamboat Springs, CO · 2 fatalities
- MOONEY M20K
2024-03-25 · St. Augustine, FL · 2 fatalities
- CESSNA 414
2023-01-18 · Modesto, CA · 1 fatality