Empire Airlines Cessna 208B accident
Cessna 208B · Accident: loss of engine power during initial climb
From Portland International Airport (PDX) to Roseburg Regional Airport (RBG)
Event
- NTSB case
- SEA06LA031
- 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
- Charter & commuter
- 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
- N753FE
- Operator
- Empire Airlines
- Onboard fatalities
- Unknown
- Route
- From Portland International Airport (PDX), Portland, ORTo Roseburg Regional Airport (RBG), Roseburg, OR
- 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 135: Air Taxi & Commuter
- 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
- Initial climb
- 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
- Loss of engine power
- 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
- Antenna
- 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
- Reason for occurrence undetermined
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 during takeoff, "after becoming airborne, the airplane quit accelerating and a positive climb rate was not established." He pushed the power lever all the way forward, but did not feel a response from the airplane. Witnesses reported that the airplane became airborne, but failed to gain altitude and struck an antenna array and a fence off the departure end of the runway. The airplane continued across a slough, struck an embankment and came to rest about 900 feet from the departure end of the runway on a golf course located adjacent to the airport. Examination of the airplane revealed no pre-mishap airframe anomalies. Examination of the engine revealed that the compressor and power turbines displayed moderate circular rubbing damage to the blades suggesting engine operation at impact, likely in the low to mid power range. Examination of the airframe and engine revealed no anomalies that would have prevented the engine from producing power prior to impact. The reason for the partial loss of engine power was not determined.
Probable cause
A partial loss of engine power for an undetermined reason during the initial takeoff climb resulting in an in-flight collision with objects.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06LA031
- Event ID
- 20051229X02024
- Case number
- SEA06LA031
- 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: f52eb151845a0c03ee6f1f9f14a22b7d4df40469429a213e550a24244e3e47eb; retrieved 2026-09-18T14:56:27.717Z.