MIA07LA140 · Cessna 208B
Paragon Air Express Cessna 208B · Accident: total loss of engine power (mechanical failure) en route
From Mobile Downtown Airport (BFM) to Tampa International Airport (TPA)
Event
- NTSB case
- MIA07LA140
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 208B
- Aircraft type
- Cessna 208
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N702PA
- Operator
- Paragon Air Express
- Onboard fatalities
- Unknown
- Route
- From Mobile Downtown Airport (BFM), Mobile, ALTo Tampa International Airport (TPA), Tampa, FL
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Total loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was on a repositioning flight to Tampa, Florida. He was cruising at 11,000 feet msl when, with no warning or spool down time, the engine failed. The engine indications instantly went to zero. The pilot declared an emergency to the air traffic controller and was advised that the nearest airport was 29 miles away. He maneuvered the airplane toward the airport and went through the engine failure procedures. The attempts to restart the engine were unsuccessful. The pilot configured the airplane for best glide speed. After gliding for 22 miles, the airplane's altitude was about 300 feet msl. The pilot slowed the airplane to just above stall speed before impacting small pine trees pulling back on the yoke and stalling the airplane into the trees. The engine was examined at Pratt and Whitney of Canada, with Transportation Safety Board of Canada oversight. The engine compressor turbine blades were fractured at varying heights from the roots to approximately half of the span. Materials analysis determined the blade fractures to display impact damage and overheating. The primary cause of the blade fractures could not be determined. There were no other pre-impact anomalies or operational dysfunction observed to any of the engine components examined. Impact damage to the blade airfoils precluded determination of the original fracture mechanism.
Probable cause
A total loss of engine power during cruise flight due to the fracture and separation of the compressor turbine blades for undetermined reasons. Contributing to the accident was the unsuitable terrain for a forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA07LA140
- Event ID
- 20070919X01415
- Case number
- MIA07LA140
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e94dcee3a6b6cf9acd16bd74031f2c566618e64ad9f8dc06f4b6d3a86b37d745; retrieved 2026-09-22T03:27:18.341Z.