NYC91FA171 · Piper PA-28-201T
Piper PA-28-201T · Accident: loss of control in flight en route
From Lancaster Airport (LNS) to Wilkes-Barre/Scranton International Airport (AVP)
Event
- NTSB case
- NYC91FA171
- 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
- 2 · 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
- Instrument Meteorological Cond
Piper PA-28-201T
- 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
- N8271B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lancaster Airport (LNS), Lancaster, PATo Wilkes-Barre/Scranton International Airport (AVP), Wilkes-Barre, 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
- 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
- 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 PILOT HAD FLOWN TO LANCASTER, PA. TO PICK UP THE 'BEST MAN' FOR HIS WEDDING. THE PILOT FILED AN IFR FLIGHT PLAN AND DEPARTED IN IFR CONDITIONS. APPROXIMATELY 15 MINUTES LATER, THE PILOT REPORTED THAT HE HAD LOST THE HORIZON INDICATOR, BUT WAS GOING TO CONTINUE TO HIS DESTINATION. THE CONTROLLER ISSUED A CLEARANCE TO CLIMB TO 6,000 FT. AND A SHORT TIME LATER, THE PILOT STATED '...ITS PRETTY HAZY HERE BUT I KNOW WE'RE ON TOP BUT I DON'T KNOW IF I WANT TO GO ANY HIGHER.' SHORTLY THEREAFTER, THE PILOT REPORTED THE 'ELECTRIC COMPASS AND TURN AND BANK INDICATOR' HAD FAILED. ACCORDING TO RADAR DATA, THE MAXIMUM ALTITUDE ATTAINED BY N82718B WAS 5,700 FT. POST ACCIDENT EXAMINATION OF THE AIRPLANE'S VACUUM SYSTEM REVEALED NO EVIDENCE OF A PRE IMPACT FAILURE. TOXICOLOGY TEST REVEALED A LEVEL OF 1.1 MG/KG OF ANTIHISTAMINE IN THE PILOT'S BODY.
Probable cause
THE PILOT'S LOSS OF AIRPLANE CONTROL DUE TO SPATIAL DISORIENTATION/VERTIGO. FACTORS RELATED TO THE ACCIDENT WERE THE PILOT'S USE OF AN ANTIHISTAMINE AND SELF INDUCED PRESSURE TO COMPLETE THE FLIGHT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC91FA171
- Event ID
- 20001212X17645
- Case number
- NYC91FA171
- 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: 2b3461b15e1e5ebdb3531c9a8b8674c86b714a326dc83a9b141f3cffb7e9a5dc; retrieved 2026-09-21T01:43:43.438Z.