SEA90FA064 · Cessna 182M
Cessna 182M · Accident: in flight collision with object on approach
From 069 · Petaluma, CA to Southwest Oregon Regional Airport (OTH)
Event
- NTSB case
- SEA90FA064
- 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
- 3 · all aircraft and ground
- Ground fatalities
- 0
- 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
- Instrument Meteorological Cond
Cessna 182M
- Aircraft type
- Cessna 182
- 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
- N71779
- Operator
- Delchini, Mario J · private individual
- Onboard fatalities
- Unknown
- Route
- From 069 · Petaluma, CATo Southwest Oregon Regional Airport (OTH), North Bend, 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 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
- Approach · IFR missed approach
- 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 › IFR procedure, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT THE END OF A CROSS COUNTRY FLIGHT, THE PILOT WAS CLEARED TO THE ILS 4 APPROACH. THE PILOT INITIATED A MISSED APPROACH DURING THE FIRST ATTEMPT AND WAS INSTRUCTED TO HOLD AT THE FAF. THE PILOT WAS THEN CLEARED FOR THE ILS APPROACH FOR THE SECOND TIME. THE PILOT THEN TURNED TOWARD THE AIRPORT WITHOUT COMPLETING THE PUBLISHED PROCEDURE TURN AND PROCEDED INBOUND TO THE RUNWAY AT AN ALTITUDE 3,000 FEET ABOVE THE MINIMUM PUBLISHED ALTITUDE. THE RADAR RETURNS INDICATE THAT THE FLIGHT WAS ESTABLISHED ON THE LOCALIZER WITH RADAR CONTACT LOST WHEN THE AIRPLANE DESCENDED BELOW 3,100 FEET AND WAS DIRECTLY OVER THE RUNWAY. THE AIRPLANE COLLIDED INTO HILLY TERRAIN APROXIMATELY 2 MILES NORTH EAST OF THE RUNWAY ON A HEADING OF 40 DEGREES.
Probable cause
THE PILOT DID NOT FOLLOW THE PUBLISHED IFR PROCEDURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA90FA064
- Event ID
- 20001212X23025
- Case number
- SEA90FA064
- 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. 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: 299f730375153b0d2c49d4cae2cd1848de4c675e98330d03cf8a39b36c69a1fe; retrieved 2026-09-21T02:47:55.810Z.