FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL98FA023 · Beech A100

10 Dec 1997 · Charlotte, NC, United States

Beech A100 · Accident: in flight collision with object on approach

From Greenbrier Valley Airport (LWB) to Concord-Padgett Regional Airport (JQF)

Report a problem

Event

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

Beech A100

Aircraft type
Beechcraft 100
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
N30SA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Greenbrier Valley Airport (LWB), Lewisburg, WVTo Concord-Padgett Regional Airport (JQF), Concord, 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 · IFR final 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
In flight collision with object
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
Tree(s)
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 › Decision height, not complied with
  • Pilot in command › Missed approach, not performed

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

NTSB narrative

Following a missed approach at the destination, the pilot requested weather information for two nearby airports. One airport was 53 miles northeast with a cloud ceiling of 900 feet, and visibility 6 miles. The pilot opted for the accident airport, 21 miles southwest, with an indefinite ceiling of zero, & visibility 1/4 mile. After completing the second missed approach, the flight proceeded to the accident airport. Radar vectors were provided to the ILS runway 36L. On the final approach, the flight veered to the right of the localizer and descended abruptly. Last recorded altitude for the flight was below the decision height. Investigation revealed no anomalies with the airport navigational aids for the approach, and the airplane's navigation receivers were found to be operational. Postmortem examinations of the pilot did not reveal any pre-existing diseases, and toxicological examinations were negative for alcohol & other drugs.

Probable cause

The pilot's continued approach below decision height without reference to the runway environment, and his failure to execute a missed approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL98FA023
Event ID
20001208X09254
Case number
ATL98FA023
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1997-12-11.
  • API snapshot SHA-256: 6ef2de813a1a359a06ed54b1e1036328e894dbc87f7a33ecb734efc0f838a1cb; retrieved 2026-09-20T22:44:01.120Z.