SEA07LA001 · Oneil Oneil Glassair II-S
Oneil Oneil Glassair II-S · Accident: partial loss of engine power (non-mechanical) during initial climb
From Richland Airport (RLD) to Richland Airport (RLD)
Event
- NTSB case
- SEA07LA001
- 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
Oneil Oneil Glassair II-S
- Aircraft type
- Oneil GLASSAIR II-S
- 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
- N204BL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Richland Airport (RLD), Richand, WATo Richland Airport (RLD), Richand, WA
- 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
- 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
- Partial loss of engine power (non-mechanical)
- 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
After takeoff and reaching an altitude of 1,000 feet above the ground, the engine surged and a reduction of power was observed; attempts to restore engine power were unsuccessful. The pilot decided to attempt a return to the airport; however, he elected to land in an adjacent field after determining he would not be able to make the runway. Subsequent impact with trees resulted in substantial damage to the airplane. A post-accident engine run did not reveal any anomalies which would have precluded normal operations. The reason for the partial loss of power could not be determined.
Probable cause
Loss of partial engine power for undetermined reasons during the initial climb after takeoff. Trees were a factor during the landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07LA001
- Event ID
- 20061003X01444
- Case number
- SEA07LA001
- 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: 38ea026b291c76ec61c17a50051ff16b53c253649a340b3647fd16adbcd781f3; retrieved 2026-09-21T18:40:22.055Z.