ATL83LLQ01 · Beech 35
Beech 35 · Accident: in flight encounter with weather during initial climb
From Hazard, KY to C · Charlotte, NC
Event
- NTSB case
- ATL83LLQ01
- 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
- 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 35
- Aircraft type
- Beechcraft 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
- N188CB
- Operator
- Frnklin Boggs
- Onboard fatalities
- Unknown
- Route
- From Hazard, KYTo C · Charlotte, 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
- Initial climb
- 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 encounter with weather
- 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 › Airspeed, not maintained
- Pilot in command › Altitude, not maintained
- Pilot in command › Became lost/disoriented, inadvertent
Approximate · Estimated position: the centre of Hazard, KY, the place the record names. Not the accident site.
NTSB narrative
THE PILOT REPORTED THAT THE AIRPORT WAS LOCATED IN A VALLEY, AND DUE TO THE TERRAIN, IT WAS NECESSARY TO TAKEOFF ON RUNWAY 17 WITH A QUARTERING LEFT TAIL WIND. HE REPORTED THAT A MOUNTAIN WAS LOCATED CLOSE TO THE RUNWAY CENTERLINE (TO THE RIGHT) AS WELL AS POWER LINES AND OTHER HAZARDS. REPORTEDLY, THE AIRCRAFT WAS MANEUVERED 200 FT LEFT OF THE CENTERLINE AS IT WAS CONFIGURED FOR A CLIMB. THE PILOT REPORTED THAT AT ABOUT 500 FT AGL, HE ENCOUNTERED WIND SHEAR OR A DOWNDRAFT, THE AIRSPEED DROPPED FROM 110 TO JUST UNDER 90 MPH AND SOME ALTITUDE WAS LOST. REPORTEDLY, HE APPLIED FULL POWER, THEN REALIZED HE HAD BECOME TEMPORARILY DISORIENTED WHEN HE SAW THAT HIS HEADING HAD CHANGED 20 DEG TO THE LEFT. AS HE ATTEMPTED TO CORRECT THE SITUATION, THE PLANE STRUCK SEVERAL TREES, THEN HIT THE GROUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83LLQ01
- Event ID
- 20020917X04386
- Case number
- ATL83LLQ01
- 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: 865589a575ff704f1b03889a8d6f3632e521f3e4d1d8c21d743faa2729c2bf9a; retrieved 2026-09-21T18:05:42.293Z.