FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14FA288 · Piper PA-46-500TP

13 Jun 2014 · White Plains, NY, United States Possible conflict

Piper PA-46-500TP · Accident: loss of control in flight during initial climb

From Westchester County Airport (HPN) to Portland International Jetport (PWM)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA14FA288
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
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-46-500TP

Aircraft type
Piper PA-46
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
N5335R
Onboard fatalities
Unknown
Route
From Westchester County Airport (HPN), White Plains, NYTo Portland International Jetport (PWM), Portland, ME
Aircraft age
About 13 years (built 2001)
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
Initial climb
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
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot arrived at the fixed-base operator on the morning of the accident and requested that his airplane be brought outside and prepared for an immediate departure; this occurred 1 hour 15 minutes before his scheduled departure time. Radar data showed that the airplane departed 23 minutes later. According to air traffic control data, shortly thereafter, the ground and departure controllers contacted the tower controller and asked if the airplane had departed yet; the tower controller responded, "I have no idea. We have zero visibility." Weather conditions about the time of the accident included a 200-ft overcast ceiling with about 1/4-mile visibility.

Only five radar targets identified as the accident airplane were captured, and all of the targets were located over airport property. The first three radar targets began about midpoint of the 6,500-ft-long runway, and each of these targets was at an altitude of about 60 ft above ground level (agl). The final two targets showed the airplane in a shallow right turn, consistent with the published departure procedure track, at altitudes of 161 and 261 ft agl, respectively. The final radar target was about 1/2 mile from the accident site. Witnesses reported observing the airplane impact trees in a wings-level, slightly right-wing-down attitude at high speed. Examination of the wreckage revealed no preimpact mechanical malfunctions or anomalies of the airplane.

The pilot's personal assistant reported that the pilot had an important meeting that required his attendance on the day of the accident flight. His early arrival to the airport and his request to have the airplane prepared for an immediate departure were actions consistent with self-induced pressure to complete the flight. Due to the poor weather conditions, which were expected to continue or worsen, he likely felt pressure to expedite his departure to ensure he was able to make it to his destination and to attend the meeting. This pressure may have further affected his ability to discern the risk associated with departing in low-visibility and low-ceiling conditions.

As noted, the weather conditions were so poor that the local air traffic controller stated that he could not tell whether the airplane had departed. Such weather conditions are highly conducive to the development of spatial disorientation. Further, the altitude profile depicted by the radar data and the airplane's near wings-level attitude and high speed at impact were consistent with the pilot experiencing a form of spatial disorientation known as "somatogravic illusion," in which the pilot errantly perceives the airplane's acceleration as increasing pitch attitude, and efforts to hold the nose down or arrest the perception of increasing pitch attitude can exacerbate the situation. Such an illusion can be especially difficult to overcome because it typically occurs at low altitudes after takeoff, which provides little time for recognition and subsequent corrective inputs, particularly in very low-visibility conditions.

Probable cause

The pilot's failure to maintain a positive climb rate after takeoff due to spatial disorientation (somatogravic illusion). Contributing to the accident was the pilot's self-induced pressure to depart and his decision to depart in low-ceiling and low-visibility conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA288
Event ID
20140613X91656
Case number
ERA14FA288
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. 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: ebbabea448de4552fa9b5285e1f1fa9d1b7fc952b9fb99821e18c685528cfad5; retrieved 2026-09-14T17:19:35.660Z.