FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD97LA058 · Bellanca 8KCAB

28 Mar 1997 · Warrenton, VA, United States

Bellanca 8KCAB · Accident: loss of control on ground/water during landing

From Warren Memorial Replacement Hospital Heliport (VA36) to an unrecorded destination

Report a problem

Event

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

Bellanca 8KCAB

Aircraft type
Bellanca 8
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
N1118E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Warren Memorial Replacement Hospital Heliport (VA36), FORK UNION, VATo 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 · landing roll
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
Loss of control on ground/water
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 › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained

Approximate · Estimated position: the centre of Warrenton, VA, the place the record names. Not the accident site.

NTSB narrative

According to the pilot, the wind was approximately 16 to 18 knots with the windsock at a direct 90 degree crosswind to runway 14. The pilot stated that he did a go-around on his first landing attempt, because the two main gear did not touch at the same time. According to him, on the second landing attempt, the airplane encountered a gust of wind, and the tail shifted, which he corrected with aileron. The pilot stated that after passing trees on the side of the runway, a second gust of wind caught the tail, and the airplane went off the runway. According to the pilot, he added power to avoid a nose over and to jump a ditch. The pilot shut down engine power in an unsuccessful attempt to avoid striking trees, which were located adjacent to the runway at about three-quarters of its length.

Probable cause

the pilot's inadequate compensation for wind conditions and failure to maintain directional control of the airplane. The crosswind was a related factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD97LA058
Event ID
20001208X07562
Case number
IAD97LA058
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: 354c0e5894de353e7ebbd0c42d8169ab65720f2ab839132ca3b54ae48850e6cb; retrieved 2026-09-22T20:05:58.564Z.