IAD01FA053 · Piper PA-28R-180
Piper PA-28R-180 · Accident: in flight collision with terrain/water en route
From Leesburg Executive Airport (JYO) to Brokenstraw Airport (P15)
Event
- NTSB case
- IAD01FA053
- 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
- Visual Meteorological Cond
Piper PA-28R-180
- Aircraft type
- Piper PA-28
- 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
- N7680J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Leesburg Executive Airport (JYO), Leesburg, VATo Brokenstraw Airport (P15), Pittsfield, PA
- 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 collision with terrain/water
- 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 › Incapacitation(loss of consciousness)
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot planned a direct flight from Leesburg, Virginia, to Pittsfield, Pennsylvania, which would have required a course of 344 degrees magnetic. Examination of radar data revealed the airplane initiated the flight on an approximate ground track of 340 degrees, and continued on that track for about 15 minutes. During the next hour, the airplane performed three consecutive left-hand orbits and then rolled out on a ground track of 240 degrees. The airplane flew for about an hour on that track, and the last radar identification was about 5 miles from the accident site. Examination of the airplane and engine revealed no mechanical deficiencies. According to a friend of the pilot's, the pilot had a history of "passing out," with no particular reason or trigger identified. She stated that the pilot had passed out three times in the 2 weeks prior to the accident, and once the day before the accident. The pilot's doctor reported that the pilot had undergone extensive testing to determine a cause for his recurring loss of consciousness. During the testing process, the pilot was instructed not to fly his airplane, until a cause could be identified for the episodes. Four months prior to the accident, the pilot was diagnosed with "vascular syncope," a nervous system reaction in which the heart rate and blood pressure drop for no reason. On his last FAA medical application, dated three months prior to the accident, the pilot stated he had never experienced dizziness or fainting spells, unconsciousness, or high blood pressure. A review of every FAA medical application on file for the pilot revealed he never reported any health problems.
Probable cause
The pilot's loss of consciousness due to a medical condition, which resulted in his failure to maintain control of the airplane and subsequent impact with rising terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD01FA053
- Event ID
- 20010514X00932
- Case number
- IAD01FA053
- 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, 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: 7721325d1c4b3f782fcc8722ec12a8a0774e1a52deff7e7430133d3d72ef0df3; retrieved 2026-09-20T20:34:39.470Z.