IAD98LA045 · Cessna 172N
Aero Safety Flight Training Cessna 172N · Accident: hard landing
From Culpeper Regional Airport (CJR) to Bay Bridge Airport (W29)
Event
- NTSB case
- IAD98LA045
- 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
Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N734MN
- Operator
- Aero Safety Flight Training
- Onboard fatalities
- Unknown
- Route
- From Culpeper Regional Airport (CJR), CULPEPPER, VATo Bay Bridge Airport (W29), MD
- 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 › Directional control, not maintained
- Pilot in command › Flare, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A witness reported the airplane landed hard on the nose wheel and continued to bounce down the runway. Each bounce increased in severity and magnitude. The pilot lost directional control, and the airplane departed the runway and struck a wind direction indicator to the right of the landing surface. The pilot said he applied right rudder during the landing, but did not recall applying brakes. He reported the airplane had no mechanical deficiencies. An operational check of the airplane's braking system by an FAA Airworthiness Inspector revealed no discrepancies.
Probable cause
the pilot's improper flare, improper recover from a bounced landing, and failure to maintain directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD98LA045
- Event ID
- 20001211X09879
- Case number
- IAD98LA045
- 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: a8556b5a2ec8dd80eb784448d361ee7961cad7fafe85f280894f13dfe8a34254; retrieved 2026-09-22T17:53:45.108Z.