FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL82FA033 · Beechcraft BE-58

3 Jan 1982 · Pinehurst, NC, United States

Beechcraft BE-58 · Accident: loss of control in flight on approach

From Fulton County Airport Brown Field (FTY) to Moore County Airport (SOP)

Report a problem

Event

NTSB case
ATL82FA033
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
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

Beechcraft BE-58

Aircraft type
Beechcraft BE-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
N10VS
Operator
Alfred B. Von Schlegell · private individual
Onboard fatalities
Unknown
Route
From Fulton County Airport Brown Field (FTY), Atlanta, GATo Moore County Airport (SOP), Southern Pines, NC
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
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
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 › IFR procedure, improper
  • Pilot in command › Impairment(alcohol)

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

NTSB narrative

THE AIRCRAFT DEPARTED FULTON COUNTY AIRPORT AT 0306 EST AND CLIMBED TO 13000 FEET MSL. THE FLIGHT WAS ROUTINE UNTIL APPROXIMATELY 0422 WHEN THE PILOT OF THE UNPRESSURIZED BEECH 58 REQUESTED AND WAS GIVEN A LOWER ALTITUDE. DURING THE NEXT 35 MINUTES THE AIRCRAFT TURNED IN THE WRONG DIRECTION AT LEAST 3 TIMES, COULD NOT MAINTAIN ALTITUDE, AND GENERALLY HAD TROUBLE FOLLOWING INSTRUCTIONS. THE AIRCRAFT COLLIDED WITH TREES IN A 30-45 DEGREE NOSE DOWN ATTITUDE.THE RESULTS OF THE TOXICOLOGICAL EXAMINATION REVEALED A BLOOD ETHANOL CONCENTRATION OF 200 MG%. A FLIGHT CHECK OF THE SAND HILLS VOR ON 1/4/82 REVEALED THAT THE VOR-A APPROACH WAS OUT OF TOLERANCE STRUCTURE AND A NOTAM WAS ISSUED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL82FA033
Event ID
20020917X01720
Case number
ATL82FA033
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: 9be26909affe08e8cff7b79541766fd760c7874e3f83e378fd0ef712bf45f897; retrieved 2026-09-21T08:40:18.322Z.