SEA92LA132 · Cessna 210D
Cessna 210D · Accident: in flight collision with object on approach
From Provo Municipal Airport (PVU) to Burley Municipal Airport (BYI)
Event
- NTSB case
- SEA92LA132
- 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
- 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
- Visual Meteorological Cond
Cessna 210D
- Aircraft type
- Cessna 210
- 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
- N3739Y
- Operator
- Blaine, Comer · private individual
- Onboard fatalities
- Unknown
- Route
- From Provo Municipal Airport (PVU), Provo, UTTo Burley Municipal Airport (BYI), Burley, ID
- 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 · VFR go-around
- 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
- 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 › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT OF THE CESSNA 210D WAS ATTEMPTING TO LAND ON A RUNWAY WHICH HAD BEEN CLOSED BY FAA NOTAM AND A YELLOW X OVER THE RUNWAY IDENTIFICATION NUMBERS. HE DID NOT CONTACT THE ON FIELD FAA FLIGHT SERVICE STATION (FSS) FOR AIRPORT ADVISORIES PRIOR TO THE LANDING, AND DID NOT NOTICE THE TEMPORARY BARRIERS AND EQUIPMENT ON THE RUNWAY UNTIL HE WAS BEGINNING HIS LANDING FLARE. HE EXECUTED A GO AROUND, BUT IMPACTED A BARRIER WITH THE LEFT ELEVATOR. THE ELEVATOR DANGLED FROM THE AIRCRAFT UNTIL THE PILOT WAS ABLE TO LAND ON AN ADJACENT TAXIWAY, WHEREUPON THE ELEVATOR SEPARATED FROM THE AIRCRAFT. AFTER THE AIRCRAFT IMPACTED THE BARRIER, THE FSS PERSONNEL WERE UNABLE TO ESTABLISH RADIO CONTACT WITH THE PILOT ON THE AIRPORT ADVISORY FREQUENCY (123.6), BUT WERE ULTIMATELY ABLE TO MAKE CONTACT ON ANOTHER FREQUENCY (122.8).
Probable cause
THE PILOT'S INADEQUATE VISUAL LOOKOUT. FACTORS INCLUDE FAA NOTAMS NOT BEING OBTAINED, FLIGHT SERVICE STATION SERVICES NOT BEING USED, AND AN OBJECT (TEMPORARY BARRIER) ON THE RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA132
- Event ID
- 20001211X15008
- Case number
- SEA92LA132
- 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: fdc3015a10403a4376d9e5e7241a349675c56d938e117cb55edb807c7ff09f1b; retrieved 2026-09-23T03:01:25.922Z.