ATL92LA168 · Beech C23
Piedmont Aviation Services Beech C23 · Accident: hard landing
From Charlotte-Monroe Executive Airport (EQY) to an unrecorded destination
Event
- NTSB case
- ATL92LA168
- 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 C23
- Aircraft type
- Beechcraft 23
- 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
- N63892
- Operator
- Piedmont Aviation Services
- Onboard fatalities
- Unknown
- Route
- From Charlotte-Monroe Executive Airport (EQY), Monroe, 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
- 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 › Touchdown, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PRIVATE PILOT WAS MAKING A PRACTICE LANDING AT A LOCAL AIRPORT. AS THE NOSE GEAR CONTACTED THE RUNWAY SURFACE, HE APPLIED THE WHEEL BRAKES, AND THE NOSE DROPPED TO AN 'UNUSUALLY LOW NOSE-DOWN ATTITUDE.' THE AIRCRAFT THEN VEERED SHARPLY TO THE LEFT AND DEPARTED THE RUNWAY SURFACE. AN INSPECTION OF THE ACCIDENT SITE REVEALED THAT THE PROPELLER CONTACTED THE RUNWAY SHORTLY AFTER NOSE GEAR TOUCHDOWN. THE WHEEL BRAKES AND NOSE WHEEL STEERING SYSTEMS SHOWED NO EVIDENCE OF PRE-ACCIDENT MALFUNCTION OR FAILURE. AN FAA INSPECTOR REPORTED THAT TWO SUPPORT TUBES ON THE NOSE GEAR FRAME WERE BROKEN, AND THERE WAS EVIDENCE OF FULL NOSE GEAR STRUT COMPRESSION DURING THE TOUCHDOWN. THE PILOT HAD OBTAINED HIS PRIVATE PILOT CERTIFICATE ABOUT THREE WEEKS PRIOR TO THE ACCIDENT, AND HAD LOGGED ABOUT 11 HOURS AS PILOT-IN-COMMAND.
Probable cause
THE PILOT'S IMPROPER TOUCHDOWN, RESULTING IN AN OVERLOAD FAILURE OF THE NOSE GEAR ATTACHMENT SUPPORT TUBES. FACTORS WERE THE LACK OF TOTAL EXPERIENCE OF THE PILOT AND THE DITCH ADJACENT TO THE RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL92LA168
- Event ID
- 20001211X15330
- Case number
- ATL92LA168
- 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: 181de47ca68ba6b132571ef347493a40e4fc8eb19cfa0585eee59852e62b8ec3; retrieved 2026-09-23T02:42:54.157Z.