IAD01FA070 · Piper PA-32R-301
Piper PA-32R-301 · Accident: in flight collision with object on approach
From AIY · Atlantic City, NJ to Westchester County Airport (HPN)
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
- IAD01FA070
- 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-32R-301
- 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
- N13VH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From AIY · Atlantic City, NJTo Westchester County Airport (HPN), White Plains, NY
- 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 · IFR missed approach
- 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
- 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
- Tree(s)
- 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 › Aircraft control, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The instrument rated pilot obtained weather briefings for his destination, which reported instrument meteorological conditions, including fog, mist, low visibilities and ceilings. The pilot then departed and flew to his destination, where he was cleared for an ILS approach. The airplane flew along the localizer course, and about a 1/2-mile from the approach end of the runway, the airplane initiated a climb and made a left turn toward the east. The airplane continued to turn left and flew north. It then began a series of left and right hand ascending and descending turns to various altitudes. During the last 3 minutes of flight, the airplane made 18 ascents and descents, with vertical speeds varying between positive 4,600 and negative 6,000 fpm, and it's altitude varied between 600 and 1,800 feet msl. Two witnesses heard the airplane fly loudly overhead before it collided with terrain, and reported that the weather was very foggy. At the time of the accident, weather reported at the airport included zero visibility, fog, vertical visibility 100 feet. According to FAA Flight Training Handbook Advisory Circular (AC) 61-21A, "If neither horizon or surface references exist, the airplane's attitude must be determined by artificial means - an attitude indicator or other flight instruments. Sight, supported by other senses such as the inner ear and muscle sense, is used to maintain spatial orientation. However, during periods of low visibility, the supporting senses sometimes conflict with what is seen. When this happens, a pilot is particularly vulnerable to spatial disorientation." Two independent toxicology reports detected chlorpheniramine, a sedating antihistamine, in the pilot's blood and urine.
Probable cause
The pilot's failure to maintain control of the airplane while maneuvering in instrument meteorological conditions, due to spatial disorientation. Factors in the accident were the fog, and the pilot's use of a sedating medication.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD01FA070
- Event ID
- 20010709X01336
- Case number
- IAD01FA070
- 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: 10e057f51367663901f386160e56be949ab3bc62b09d5ffccf6c51529407e4da; retrieved 2026-09-20T20:29:25.269Z.