FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO88LA019 · Beech C-23

15 Feb 1988 · Roanoke, VA, United States

Piedmont Aviation Beech C-23 · Accident: hard landing

From Roanoke–Blacksburg Regional Airport (ROA) to Roanoke–Blacksburg Regional Airport (ROA)

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
BFO88LA019
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 C-23

Aircraft type
Beechcraft C-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
N6634R
Onboard fatalities
Unknown
Route
From Roanoke–Blacksburg Regional Airport (ROA), Roanoke, VATo Roanoke–Blacksburg Regional Airport (ROA)
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 › Flare, inadequate
  • Pilot in command › Porpoise/pilot-induced oscillation, inadvertent

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

NTSB narrative

THIS WAS THE STU PLT FIFTH TRAINING SESSION WHERE HE DID SOLO TOUCH & GO LANDINGS. DURING THIS SESSION HE MADE TEN LANDINGS WITHOUT INCIDENT. SIX LANDINGS WERE MADE WITH HIS INSTR ABOARD FOLLOWED BY FOUR SOLO LANDINGS. ACCORDING TO THE STU DURING THE FLARE FOR THE ELEVENTH LANDING THE ACFT STARTED TO PORPOISE UNCONTROLLABLY. THE ACFT LANDED ON THE NOSE GEAR WHICH COLLAPSED AND THE ACFT SLID OFF THE RUNWAY AND AN ENGINE FIRE ERUPTED. THE CARBURETOR WAS FRACTURED DURING THE IMPACT SEQUENCE. THE PLT SAFELY EXITED THE ACFT AND THE FIRE WAS EXTINQUISHED SHORTLY AFTERWARD BY AIRPORT FIRE DEPT PERSONNEL.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record BFO88LA019
Event ID
20001213X25015
Case number
BFO88LA019
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: afaa463c989b8dae3e1bb61fa3ad4e54a6ea910c30b8b61493a3270b80967a84; retrieved 2026-09-23T11:01:49.464Z.