DEN85FA009 · Bellanca 14-19-3A
Bellanca 14-19-3A · Accident: in flight encounter with weather en route
From Flagstaff Pulliam Airport (FLG) to an unrecorded destination
Event
- NTSB case
- DEN85FA009
- 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
- 1 · 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
Bellanca 14-19-3A
- Aircraft type
- Bellanca 14
- 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
- N8868R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo not recorded
- 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
- En route · cruise
- 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 encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Design stress limits of aircraft, exceeded
- Pilot in command › Flight into known adverse weather, continued
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › VFR flight into imc, initiated
- Pilot in command › Weather evaluation, poor
- Wing › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
LEFT WING FAILED INFLIGHT. THUNDERSTORMS IN AREA AT TIME OF CRASH. PILOT WAS ENROUTE FROM CALIFORNIA TO NEW JERSEY, HAD BEEN FLYING 4 HOURS, 18 MINUTES. AWAKE AT LEAST 7 HOURS. TRANSITED 1 TIME ZONE. NO RECORD OF WEATHER BRIEFING OR FLIGHT PLAN FILED. PILOT NOT INSTRUMENT RATED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN85FA009
- Event ID
- 20001214X41332
- Case number
- DEN85FA009
- 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: d81270ed82885ddcacd3129a3a8c239d8819510dec1ccecf8974173407776c6b; retrieved 2026-09-21T05:17:57.319Z.