NYC96LA013 · Piper PA-32
Piper PA-32 · Accident: in flight encounter with weather en route
From Bradley International Airport (BDL) to John Glenn Columbus International Airport (CMH)
Event
- NTSB case
- NYC96LA013
- 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
Piper PA-32
- Aircraft type
- Piper PA-32
- 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
- N39964
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bradley International Airport (BDL), Windsor Locks, CTTo John Glenn Columbus International Airport (CMH), Columbus, OH
- 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 · descent
- 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
- 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 › Flight into known adverse weather, intentional
- Pilot in command › Weather evaluation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot obtained a weather briefing and filed an IFR flight plan with an Automated Flight Service Station (AFSS). After takeoff, he climbed to his cruising altitude of 8,000 feet, which was above the clouds. En route he encountered strong headwinds, and requested a descent to 6,000 feet. ATC issued the pilot an initial descent to 7,000 feet. During the descent, he encountered severe turbulence and icing. After descending below the clouds, the pilot could not maintain altitude and made a forced landing downwind to a nearby airport. During landing, the airplane was blown off of the runway into the runway lights. The reported winds were 250 degrees at 14 knots gusting to 24 knots. During the weather briefing with the AFSS, the pilot was issued an AIRMET for light to moderate mixed/rime icing, in the clouds and precipitation, from the freezing level to 10,000 feet, and isolated severe icing in the clouds. He was given the freezing level along his route to be between 2,000 and 4,000 feet. The briefer also gave the pilot the forecast for 'strong westerly winds,' which included winds at 9,000 feet, from 280 degrees at 38 knots. The airplane was not equipped with anti-icing, or deicing equipment, except for a heated pitot tube.
Probable cause
the pilot's improper evaluation of the weather briefing, and his decision to fly into known forecasted moderate to severe icing conditions. Factors in the accident were the adverse weather conditions encountered during the flight and landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96LA013
- Event ID
- 20001207X04775
- Case number
- NYC96LA013
- 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: eac161528db5c445bf7b0a7846ebf1b186d98b3d1899e07a38239de15591c439; retrieved 2026-09-22T23:08:58.049Z.