FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC91LA232 · Piper PA46-350P

8 Sept 1991 · Dayton, OH, United States

Piper PA46-350P · Accident: airframe, component or system failure during initial climb

From an unrecorded airport to Johnson County Executive Airport (OJC)

Report a problem

Event

NTSB case
NYC91LA232
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 PA46-350P

Aircraft type
Piper PA46
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
N350MM
Operator
Arthur F. Lindquist · private individual
Onboard fatalities
Unknown
Route
From not recordedTo Johnson County Executive Airport (OJC), Olathe, KS
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
Airframe, component or system failure
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

  • Flt control syst, elevator trim indicator › Binding(mechanical)
  • Flt control syst, elevator trim indicator › Disconnected

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

NTSB narrative

DURING THE TAKEOFF ROLL THE NOSE OF THE AIRPLANE CAME OFF THE GROUND PREMATURELY. THE PILOT TRIED TO CORRECT BY ELECTRICALLY APPLYING NOSE DOWN TRIM, BUT DID NOT GET ANY RESPONSE. THE AIRPLANE CLIMBED ABOUT 50 FEET OFF THE GROUND AND THE PILOT COULD NOT LOWER THE NOSE. THE PILOT ELECTED TO ABORT THE TAKEOFF THE AIRPLANE LANDED HARD ON THE RUNWAY, VEER TO THE RIGHT, DEPARTED THE RUNWAY AND STRUCK 3 TAXIWAY LIGHTS AND A TAXIWAY SIGN. EXAMINATION OF THE AIRPLANE'S ELECTRIC ELEVATOR TRIM INDICATOR REVEALED THAT THE INDICATOR HAD MALFUNCTIONED BECAUSE A GUIDE/LODGING PIN WAS BINDING, WHICH RESULTED IN THE INDICATOR DISCONNECTING FROM THE TRACK. THE INDICATOR WAS READING FULL NOSE DOWN, AT THE SAME TIME THE ELEVATOR TRIM TAB WAS IN THE FULL NOSE UP POSITION.

Probable cause

A MALFUNCTION OF THE ELEVATOR TRIM INDICATOR AND INCORRECT POSITION OF THE TRIM TAB WHICH RESULTED IN THE PILOT ABORTING THE TAKEOFF AND A LOSS OF DIRECTIONAL CONTROL ON THE GROUND.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC91LA232
Event ID
20001212X18166
Case number
NYC91LA232
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: 737402b71f865e1f0a8538343f75e927de5ab202aa8b8ddc4013ccc452f9ffe6; retrieved 2026-09-23T03:42:49.386Z.