IAD96LA093 · Cessna 177RG
Cessna 177RG · Accident: loss of control on ground/water during landing
From an unrecorded airport to Baltimore/Washington International Thurgood Marshall Airport (BWI)
Event
- NTSB case
- IAD96LA093
- 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 177RG
- Aircraft type
- Cessna 177
- 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
- N35082
- Operator
- Ronald A. Silkworth · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Baltimore/Washington International Thurgood Marshall Airport (BWI), Baltimore, 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 · 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he had just taken off to the north to practice landings on the 5000-foot long and 100-foot wide runway. The traffic pattern was normal with a normal landing. As the airplane was rolling on the runway, he applied power for a touch-and-go. The airplane veered left causing the right wing to raise. The pilot stated that in order to stabilize the airplane, it was necessary to roll off the runway onto the grass. The pilot wrote that 'once on the grass, running parallel to the runway, control of steering and braking was diminished and insufficient to avoid the taxi-way marker (2000 feet remaining runway marker) which was struck by the left side of the stabilator, causing the damage. The certificated flight instructor passenger commented that he was looking out his window and not paying attention. The winds in the local area were recorded from the west southwest at approximately 10 knots.
Probable cause
The pilot-in-command's failure to maintain control of the airplane during landing. A factor in this accident was the CFI-rated pilot/passenger's inattention.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD96LA093
- Event ID
- 20001208X05800
- Case number
- IAD96LA093
- 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: 8cd2ed67627e1814ac0b81ade2fc0db21a6921f7c826e9b811a54befdca8dc2b; retrieved 2026-09-22T22:28:32.813Z.