SEA04CA068 · Yakovlev Yak 54
Yakovlev Yak 54 · Accident while maneuvering
From Friday Harbor, WA to Friday Harbor, WA
Event
- NTSB case
- SEA04CA068
- 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
Yakovlev Yak 54
- Aircraft type
- Yakovlev YAK-54
- 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
- N14026
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Friday Harbor, WATo Friday Harbor, 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
- Maneuvering
- 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
- Miscellaneous/other
- 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
- Pilot in command › Proper alignment, not attained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
In a written statement the pilot reported that the purpose of the flight was to practice aerobatics in the local area. He reported that shortly after rolling the airplane inverted, to accomplish a "belt check", oil appeared on the airplane's windscreen and canopy. The oil on the windscreen impaired the pilot's vision and he elected to return to the departure airport and land. He stated that the airplane touched down on the left edge of the runway, encountered rough/uneven terrain and the nose gear collapsed. The pilot stated that he had not tightened the engine oil cap prior to departure. The oil cap was later found laying on the ground in the run-up area of the airstrip.
Probable cause
The pilot's failure to properly align with the runway. Factors include rough/uneven terrain, inadequate preflight planning and diminished forward visibility.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04CA068
- Event ID
- 20040427X00520
- Case number
- SEA04CA068
- 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: 95d55b188f9611e4fdc03a35488e850c2eba41f97f816f80bbcdb7319ddc1b87; retrieved 2026-09-22T07:45:39.759Z.