ERA13FA253 · Piper PA-34-200T
Campbell Associates At Curtiss Aero Piper PA-34-200T · Accident: loss of control in flight en route
From Laurence G Hanscom Field (BED) to Griffiss International Airport (RME)
Event
- NTSB case
- ERA13FA253
- 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
- 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
- Instrument Meteorological Cond
Piper PA-34-200T
- Aircraft type
- Piper PA-34
- 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
- N31743
- Onboard fatalities
- Unknown
- Route
- From Laurence G Hanscom Field (BED), Bedford, MATo Griffiss International Airport (RME), Rome, NY
- Aircraft age
- About 35 years (built 1978)
- 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
- Defining eventThe 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
- Loss of control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft structures
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The volunteer medical transport flight was established on course toward an en route navigational fix. Upon reaching the fix, the flight was expected to continue toward the initial approach fix at the destination airport in preparation for an instrument approach; however, about 5 miles southeast of the en route fix, the airplane began to deviate off course. When asked by an air traffic controlller about the reason for the deviation, the pilot stated that the airplane had turned "the wrong way" and indicated that he had incorrectly loaded the instrument approach into the airplane's GPS. The controller provided a vector to the pilot to return the airplane to the previously established course, and the pilot acknowledged. About 1 minute later, radar contact with the airplane was lost.
Radar data indicated that the airplane entered a rapidly-descending left turn in the final moments of the flight during which it reached an estimated 80-degree left bank, lost about 3,700 feet of altitude in 36 seconds, and accelerated to an airspeed of about 240 knots before breaking up. All fracture surfaces exhibited failure characteristics consistent with overload. Examination of the engines revealed no anomalies. Analysis of weather information for the area of the accident site indicated that the airplane was likely operating in instrument meteorological conditions at the time of the accident but that icing conditions likely were not present in the immediate vicinity.
The restricted visibility, turbulence, the airplane's unexpected off-course turn, the pilot's resulting distraction with the operation and configuration of the GPS, and possibly his sudden need to fly the airplane without the aid of the autopilot would have been conducive to the development of spatial disorientation. The resulting ground track, rapid turning descent, and breakup were consistent with a loss of control as a result of spatial disorientation.
Probable cause
The pilot's loss of control due to spatial disorientation in instrument meteorological conditions, which resulted in an exceedance of the airplane's design stress limitations, and a subsequent in-flight breakup.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13FA253
- Event ID
- 20130524X84708
- Case number
- ERA13FA253
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: f40be97f2a54c9c733e674a25c81d2dbb75c77f1c961bd354d774db7e633beb6; retrieved 2026-09-14T15:57:10.859Z.