ATL82DA096 · Beech 65-A90
N.W. Financial Beech 65-A90 · Accident: hard landing
From Lynchburg Regional Airport - Preston Glenn Field (LYH) to Smith Reynolds Airport (INT)
Event
- NTSB case
- ATL82DA096
- 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
- Visual Meteorological Cond
Beech 65-A90
- Aircraft type
- Beechcraft 65
- 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
- N7377
- Operator
- N.W. Financial
- Onboard fatalities
- Unknown
- Route
- From Lynchburg Regional Airport - Preston Glenn Field (LYH), Lynchburg, VATo Smith Reynolds Airport (INT), WINSTON, 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
- Landing · flare/touchdown
- 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
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Propeller, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
BEFORE LANDING, THE PILOT WAS ADVISED BY APPROACH CONTROL THAT BOEING 737 TRAINING WAS BEING CONDUCTED ON RUNWAY 33. THE PILOT AGREED TO LAND ON RUNWAY 21 AND HOLD SHORT OF RUNWAY 33. THE AIRCREWS CONDUCTING 737 TRAINING WERE SO ADVISED. THE AIRCRAFT WAS ON FINAL APPROACH SHORTLY AFTER THE TOWER CLOSED AT 2300 EST. THE PILOT DID NOT SEE THE RUNWAY LIGHTS, BUT AT FIRST, HE THOUGHT THEY WERE SET ON LOW INTENSITY AND COULD NOT BE SEEN WITH HANGAR AND RAMP LIGHTS IN THE BACKGROUND. AT 150 TO 200 FT AGL, HE SAW THE RUNWAY WHEN IT WAS ILLUMINATED BY HIS LANDING LIGHTS AND REALIZED THE RUNWAY LIGHTS WERE NOT ON. QUICKLY, HE DECIDED TO LAND RATHER THAN GO-AROUND AND CONFLICT WITH THE TRAFFIC USING RUNWAY 33. SHORTLY AFTER REACHING FOR THE THROTTLES TO REDUCE POWER TO IDLE AND LAND, THE PLANE STALLED FROM 20 TO 50 FT AGL AND LANDED HARD. AN INVESTIGATION REVEALED THAT THE PILOT HAD INADVERTENTLY MOVED THE PROPELLER CONTROLS TO THE REVERSE PITCH POSITION. THE PILOT HAD BEEN ON DUTY SINCE HIS FIRST TAKEOFF AT 0600.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82DA096
- Event ID
- 20020917X01697
- Case number
- ATL82DA096
- 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 1982-04-08.
- API snapshot SHA-256: 9eb2c9665db1cc6f236eedf24eebf58a33353bf8a327a5ec6bb841f6243335aa; retrieved 2026-09-24T03:26:50.549Z.