FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC98LA019 · Piper PA-34-220T

24 Oct 1997 · Philadelphia, PA, United States

Piper PA-34-220T · Accident: loss of control in flight during initial climb

From Northeast Philadelphia Airport (PNE) to Lancaster Airport (LNS)

Report a problem

Event

NTSB case
NYC98LA019
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
0 · 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
Visual Meteorological Cond

Piper PA-34-220T

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
N8371H
Operator
Morton T. Saunders · private individual
Onboard fatalities
Unknown
Route
From Northeast Philadelphia Airport (PNE)To Lancaster Airport (LNS), Lancaster, 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
Initial climb
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
Substantial

Cause areas

  • Pilot in command › Checklist, not followed
  • Pilot in command › Elevator trim, not set

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

NTSB narrative

The pilot stated that during the takeoff run, it was difficult to pitch the nose up for takeoff. The airplane became airborne and descended back onto the runway. The airplane porpoised on the runway several times before the nose and right main landing gear collapsed. The pilot reported that the flight was the first since the annual inspection. Although he checked flight control freedom before takeoff, he did not check the elevator trim position. After the accident, he realized the trim was in the full nose-down position. Additionally, the pilot reported that he did not immediately retard the power after the airplane returned to the runway and began to porpoise.

Probable cause

the pilot's failure to check the elevator trim prior to takeoff, and his failure to retard the power in a timely manner after touchdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC98LA019
Event ID
20001208X09110
Case number
NYC98LA019
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: bfb9f832e6ec8af402e93b13cfeda23d61dce1329775b1f5f80b6b4931e3b02a; retrieved 2026-09-22T18:15:20.795Z.