FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA00FA265 · Beech 58P

9 Sept 2000 · Brookhaven, MS, United States

Beech 58P · Accident: loss of control in flight on approach

From Orlando Executive Airport (ORL) to Brookhaven-Lincoln County Airport (1R7)

Report a problem

Event

NTSB case
MIA00FA265
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
2 · 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

Beech 58P

Aircraft type
Beechcraft 58
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
N58PB
Operator
James C. Barnett · private individual
Onboard fatalities
Unknown
Route
From Orlando Executive Airport (ORL), Orlando, FLTo Brookhaven-Lincoln County Airport (1R7), Brookhaven, MS
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
Approach · circling (IFR)
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
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
Stall/mush
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

  • Pilot in command › Aircraft handling, improper
  • Pilot in command › In-flight planning/decision, poor
  • Pilot in command › Stall/mush, inadvertent

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

NTSB narrative

During an IFR flight when near the destination airport, the pilot was provided the most current weather for the closest airport and also with the current altimeter setting required for the approach. The flight was cleared for the non-precision approach and according to two pilot-rated witnesses who were related to the pilot and were waiting at the airport for the flight to arrive, the weather conditions at the airport consisted of a ceiling at 500-600 feet and the visibility was 3 statute miles. No weather reporting was available at the destination airport. The airplane was observed on the downwind leg flying beneath the clouds and 644 feet abeam the runway with the landing gear extended and what appeared to be approach flaps. One of the witnesses reported that he heard a sound he associated with the propellers being placed in the low pitch position and also heard the engines increase rpm what he thought was full power for what he thought would be a missed approach. The airplane then began turning base leg when the flight had passed 10-20 degrees past the numbers; the bank angle increased to approximately 70-75 degrees and the nose then pitched down and the airplane impacted the ground. The witness reported that the engine sound did not change from the moment he heard power applied to the point of impact. Examination of the engines, propellers, and flight controls revealed no evidence of preimpact failure or malfunction. The flap selector switch was found in the down position and the left flap actuator was found in the full down position; no determination could be made as to the position of the right flap actuator. The stall speed increase with a 70 and 75-degree angle of bank is 73 percent and approximately 100 percent, respectively.

Probable cause

The poor in-flight planning/decision by the pilot for flying a close-in downwind leg, improper aircraft handling by the pilot for his executing a 70-75 degree angle of bank turning base to final while circling to land, and inadvertent stall/mush of the airplane by the pilot-in-command.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA00FA265
Event ID
20001212X22030
Case number
MIA00FA265
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: 38e6e5837e40e5bc142fd76456e722c3ddf6e5e2a54877586581590c7bd65d3a; retrieved 2026-09-20T20:52:33.835Z.