FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA037 · Beech A36

27 Oct 2024 · Pineville, LA, United States

Beech A36 · Accident: collision with terrain/object (non-CFIT) during landing

From Natchez–Adams County Airport / Hardy-Anders Field (HEZ) to an unrecorded destination

Report a problem

Event

NTSB case
CEN25LA037
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
Unknown
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
N3046K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Natchez–Adams County Airport / Hardy-Anders Field (HEZ), Natchez, MSTo not recorded
Aircraft age
About 37 years (built 1987)
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
Landing
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
Collision with terrain/object (non-CFIT)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Pole
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

  • Environmental issues › Physical environment
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that after landing on the runway, he felt a bump on the bottom of the airplane. The pilot saw metal stakes and rope and then remembered that the runway was closed. The pilot taxied to parking without further incident. The airplane sustained substantial damage to the fuselage. At the time of the accident, there was a Notice to Air Missions (NOTAM) in effect for the closure of the runway. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. After the accident, the pilot inspected the runway and found that there was a painted yellow “X” at each end of the runway. The pilot also reported that he had been notified by an airport employee about the upcoming runway closure about a month before the accident. The pilot further stated that the sun in his eyes, and various alerts while approaching the airport were distractions.

Probable cause

The airplane’s collision with a stake on a closed runway. Contributing to the accident was the pilot’s inadequate preflight planning and failure to see the closed runway markings.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA037
Event ID
20241111195471
Case number
CEN25LA037
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, cause areas. 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: b19351fbaa8d292a629222f62fb28df3768cda450d8ea075e3dba3c00a412ba1; retrieved 2026-09-16T19:27:45.595Z.