FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25FA080 · Beech A36

19 Dec 2024 · East Aurora, NY, United States

Beech A36 · Accident: loss of engine power (total) en route

From Capital Region International Airport (LAN) to Buff · Buffalo, NY

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA25FA080
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
Visual Meteorological Cond

Beech A36

Aircraft type
Beechcraft 36
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
N36WP
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Capital Region International Airport (LAN), Lansing, MITo Buff · Buffalo, NY
Aircraft age
About 45 years (built 1979)
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
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 engine power (total)
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

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

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

NTSB narrative

On December 19, 2024, at 1122 eastern standard time, a Beech A36, N36WP, was destroyed when it was involved in an accident near East Aurora, New York. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Preliminary air traffic control (ATC) data indicated that the airplane departed from Capital Region International Airport (LAN), Lansing, Michigan, on an instrument flight rules (IFR) flight plan to Westchester County Airport (HPN), White Plains, New York. About 1 hour and 20 minutes into the flight, while cruising at 12,500 ft, the pilot declared an emergency, reporting “very low power on my engine” and requesting to remain as high as possible. Air traffic control initially directed the pilot to Buffalo Niagara International Airport (BUF), Buffalo, New York, and subsequently provided vectors to Buffalo Airfield (9G0). The pilot reported that while the engine was still producing power, the airplane was no longer able to maintain altitude. He stated he did not think the airplane could reach either airport, and opted for an off-airport landing. Air traffic control provided vectors toward a freeway, but the pilot indicated he would attempt a landing in a field. Radar contact was lost shortly afterward, near the accident site. Witnesses near the accident site observed the airplane flying low, approximately 30 ft above a tree line, before seeing a black plume of smoke. Examination of the accident site revealed that the airplane initially struck a tree trunk and came to rest approximately 40 ft beyond the impact point. A postimpact fire consumed the fuselage, cockpit, and inboard wing sections. The right outboard wing exhibited crush damage near the tip, with the aileron and flap attached. The right tip tank was impact-separated, and came to rest near the base of the initial tree strike. The left outboard wing sustained multiple tree strikes, with the aileron impact-separated and the flap attached. The aft cabin and tail cone were destroyed by fire. The empennage components showed varying degrees of damage; the right horizontal stabilizer, elevator, vertical stabilizer, and rudder remained attached, while the left horizontal stabilizer and elevator were fragmented by impact forces. The engine remained partially attached to the airframe and exhibited heavy sooting and fire damage. All engine accessories remained in place and were fire damaged. Initial external examination of the engine did not reveal evidence of a catastrophic failure. The airplane was recovered for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA25FA080
Event ID
20241219199447
Case number
ERA25FA080
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. 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: 7c25f7d4a927b2aee3417eebed934c46c16bb356ce546211c4be4a513ac34521; retrieved 2026-09-15T09:00:59.306Z.