SEA04CA194 · Cessna 152
Cessna 152 · Accident: in flight collision with object during landing
From BUS · Burlington, WA to Friday Harbor, WA
Event
- NTSB case
- SEA04CA194
- 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 152
- Aircraft type
- Cessna 152
- 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
- N757RD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From BUS · Burlington, 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
- Landing · aborted
- 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
- In flight collision with object
- 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
- Pilot in command › Aborted landing, delayed
- Pilot in command › Altitude/clearance, not obtained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, the winds were calm, and he decided to land to the southeast on the 1,500-foot-long grass airstrip. He reported that he touched down approximately mid-field and "applied brakes lightly." About three-quarters of the way down the runway, he "decided to abort the landing due to high ground speed." He lifted off just prior to the end of the runway. However, "the climb was insufficient" to clear trees ahead so he turned left towards an open field. The airplane impacted trees on the edge of the field and came to rest nose down suspended in the trees. The pilot reported that the accident could have been prevented by "slower approach speed and earlier touch down.
Probable cause
The pilot's delay in executing an aborted landing and his failure to obtain altitude/clearance from trees during the aborted landing. A factor was the pilot's failure to obtain the proper touchdown point as a result of his high airspeed on approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04CA194
- Event ID
- 20040930X01547
- Case number
- SEA04CA194
- 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: 35edfe571b9b5448ccf5136fa48361d95b3ae2ff0879fb99b0aad83b3873f8f1; retrieved 2026-09-22T06:40:56.063Z.