LAX04CA309 · Cessna 172S
Cessna 172S · Accident: in flight collision with object while maneuvering
From Watsonville Municipal Airport (WVI) to Ells Field Willits Municipal Airport (O28)
Event
- NTSB case
- LAX04CA309
- 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 172S
- Aircraft type
- Cessna 172
- 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
- N897TW
- Operator
- Edward A. Warburton · private individual
- Onboard fatalities
- Unknown
- Route
- From Watsonville Municipal Airport (WVI), Watsonville, CATo Ells Field Willits Municipal Airport (O28), Willits, CA
- 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
- 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
- Destroyed
Cause areas
- Pilot in command › Altitude, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While maneuvering to locate the runway during a dark, nighttime flight, the airplane descended until colliding with trees. As the pilot approached his home base airport, he attempted to activate the pilot controlled runway lights. However, he was unsuccessful. Thereafter, the pilot performed a low altitude pass over what he believed was runway 16/34 to ascertain if a portion of the runway's lights were operating. During the maneuver, the pilot failed to detect that the airplane was not aligned with the runway. Also, the pilot failed to maintain adequate altitude to avoid colliding with trees 1/8-mile west of the airport. Neither prior to taking off, nor at any time during the accident flight, did the pilot become aware that a Notice to Airman had been issued indicating that the airport's runway lights were "out of service."
Probable cause
the pilot's inadvertent descent and controlled flight into obstacles while maneuvering to land. Contributing factors were the dark, nighttime condition, which impaired the pilot's visual perceptions, and the pilot's failure to obtain a pertinent Notice to Airman regarding inoperative runway lights.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04CA309
- Event ID
- 20041014X01630
- Case number
- LAX04CA309
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-09-02.
- API snapshot SHA-256: d9512124879468d644fa70c91a03e829ce142f0e95352e0c4d89590345fd62eb; retrieved 2026-09-21T19:09:10.677Z.