FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25FA272 · Piper PA46-500TP

20 Jul 2025 · Lititz, PA, United States

Piper PA46-500TP · Accident: loss of control in flight during initial climb

From Lancaster Airport (LNS) to State College Regional Airport (UNV)

Report a problem

Event

NTSB case
ERA25FA272
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
Ongoing
API-reported fatalities
1 · 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 PA46-500TP

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
N819MA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lancaster Airport (LNS), Lancaster, PATo State College Regional Airport (UNV), State college, PA
Aircraft age
About 10 years (built 2015)
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
Defining eventThe 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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On July 20, 2025, about 0800 eastern daylight time, a Piper PA-46-500TP Meridian airplane, N819MA, was substantially damaged when it was involved in an accident in Lititz, Pennsylvania. The pilot was the sole person on board and was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Prior to the accident flight, the airplane was towed from its hangar by line service personnel and the fuel tanks topped off with 74 gallons of Jet A and Prist fuel additive, for a total of approximately 170 gallons. Shortly afterward, airport surveillance video showed the instrument-rated private pilot arriving at the airplane. He performed a brief preflight inspection of the airplane, then entered the airplane and closed the main cabin door. The engine was started and preliminary air traffic control (ATC) data showed that the pilot called for his instrument flight rules (IFR) clearance from Lancaster Regional Airport (LNS), Lancaster Pennsylvania to State College Regional Airport (UNV), State College Pennsylvania. The readback of the clearance instructions to the clearance controller was correct and the pilot was cleared to taxi to the runway. Upon arrival at the hold-short line for departure, the ATC recording indicated that the tower controller advised the pilot to hold short while they waited for his IFR release. Three minutes later, the release was received, and the pilot was cleared for takeoff with a left turn on course. There was no readback of this instruction, and the surveillance video showed the pilot enter the runway and start his takeoff roll. Preliminary Automatic Dependent Surveillance-Broadcast (ADS-B) data showed that the airplane reached rotation speed and lifted off. As the airplane cleared the departure end of the runway, having climbed to 650 ft mean sea level at a ground speed of 136 knots, the airplane suddenly pitched down to a descent rate of -1600 feet per minute. Approximately 9 seconds later, the airplane impacted a corn field 1/4 mile from the end of the runway on an estimated heading of 070° and a descent angle of approximately 39°and the left wing slightly down. The estimated flight time from the moment the wheels left the runway to impact was approximately 20 seconds. Nineteen seconds after takeoff, the control tower attempted to establish communication with the pilot multiple times without result. The airplane came to rest 164 ft beyond the point of impact. The airframe was compressed due to impact forces. The engine and propeller created an impact crater 11 ft long, 6 ft wide, and 20 inches deep. The leading edges of the wings left an impression mark in the soil at the base of angle-cut corn stalks 3-6 inches deep along the entire wingspan. The surrounding corn throughout the debris field from the point of impact forward to the end of the debris field showed evidence of fuel blight with a strong odor of jet fuel throughout the accident site. All flight surfaces were accounted for at the accident site. The left wing, wing-flap, and left aileron were fragmented into multiple sections. The left wing separated from the fuselage at the wing root and was found laying on top of the engine. The right wing remained attached to the airframe. The leading edge was found 20 ft behind the main airplane wreckage. The tail section was intact with the left horizontal spar broken but still attached. The vertical stabilizer remained attached and upright with leading edge damage. The propeller, propeller shaft and forward reduction gear box broke free of the engine. The propeller shaft separated from the propeller and was found in the corn several feet beyond the propeller. The propeller was found 60 ft forward and to the right of the impact crater. It exhibited rotational damage including the separation of one of the four blades with two of the blades fractured at their midpoint. The recorded weather at LNS, at 0753, included: wind from 200° at 3 knots, 5 miles visibility, broken clouds at 400 ft agl and 900 ft agl, mist, temperature 25° C, dew point 24° C, and an altimeter setting of 30.03 inches of mercury. According to Federal Aviation Administration (FAA) records, the pilot held a private pilot certificate with ratings for airplane single-engine land and instrument airplane. His most recent FAA third-class medical certificate was issued on September 19, 2024. He reported on that date that he had accrued approximately 2,350 total flight hours. According to FAA and airplane maintenance records, the accident airplane was manufactured in 2015. The airplane's most recent annual inspection was completed on March 14, 2025. At the time of the inspection, the airplane had accrued approximately 1,336 total hours of operation.

The wreckage was retained for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA25FA272
Event ID
20250720200578
Case number
ERA25FA272
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: b1a079d2a6738d8cdd5889091385b825ce67f04c2dafbaea473b0b9b2481ad99; retrieved 2026-09-15T09:06:57.842Z.