ATL94FA007 · Beech S-35
Beech S-35 · Accident: loss of control in flight while maneuvering
From Burlington Alamance Regional Airport (BUY) to an unrecorded destination
Event
- NTSB case
- ATL94FA007
- 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
- 4 · 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 S-35
- Aircraft type
- Beechcraft S-35
- 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
- N8688Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Burlington Alamance Regional Airport (BUY), Burlington, NCTo not recorded
- 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
- Maneuvering
- 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
- 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 › Airspeed, not maintained
- Pilot in command › Stall, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT WAS ISSUED THE LOCAL WEATHER AND CLEARED FOR THE LOCALIZER APPROACH. THE PILOT WAS INSTRUCTED TO CONTACT UNICOM FOR AIRPORT ADVISORIES; NO UNICOM RADIO CONTACT WAS ESTABLISHED. EYEWITNESSES OBSERVED THE AIRPLANE AS IT DESCENDED OUT OF THE 400 FOOT CLOUD LAYER, ABOUT 3/4 DOWN THE RUNWAY, WITH THE AIRPLANE IN A LANDING CONFIGURATION (FLAPS AND LANDING GEAR EXTENDED). AT APPROXIMATELY THE SAME TIME, THE PILOT REPORTED A MISSED APPROACH TO APPROACH CONTROL. THE PILOT WAS INSTRUCTED TO CLIMB TO 3000 FEET THEN TURN LEFT TO 280 DEGREES; THE PILOT ACKNOWLEDGED THE INSTRUCTIONS. EYEWITNESSES SAW THE AIRPLANE IN A LEFT CLIMBING TURN WHICH CONTINUED UNTIL IT STALLED. THE AIRPLANE COLLIDED WITH THE GROUND IN A NOSE LOW ATTITUDE 1/4 MILE WEST OF THE AIRPORT. THE WRECKAGE EXAMINATION FAILED TO DISCLOSE A MECHANICAL PROBLEM.
Probable cause
WAS THE PILOT'S FAILURE TO MAINTAIN CONTROL OF THE AIRPLANE DURING A MISSED APPROACH WHICH RESULTED IN A STALL. A FACTOR WAS THE PILOT'S FAILURE TO FOLLOW IFR PROCEDURES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL94FA007
- Event ID
- 20001211X13514
- Case number
- ATL94FA007
- 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: 163980f48d240e86a02c43b69702b3f07434d7987ab8214226d879072e80ce76; retrieved 2026-09-21T00:20:34.569Z.