FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13CA438 · Cessna 182P

18 Sept 2013 · Newport News, VA, United States

Tidewater Flying Club Cessna 182P · Accident: loss of control on ground during landing

From Hampton Roads Executive Airport (PVG) to Newport News Williamsburg International Airport (PHF)

Report a problem

Event

NTSB case
ERA13CA438
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
Unknown
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 182P

Aircraft type
Cessna 182
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
N58482
Onboard fatalities
Unknown
Route
From Hampton Roads Executive Airport (PVG), Norfolk, VATo Newport News Williamsburg International Airport (PHF), Newport News, VA
Aircraft age
About 40 years (built 1973)
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
Defining eventThe 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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

The pilot indicated that during the landing, through the flare and main landing gear touchdown, all flight parameters were normal. He stated that after the nose wheel touched the ground, the airplane "veered" to the right. The pilot reported he applied full left rudder and aileron but the airplane departed the right side of the runway into a ditch. Examination of the airplane revealed substantial damage to the fuselage and engine firewall. Continuity of the rudder and nose wheel cables was verified to be correctly rigged and serviceable. The approach and landing were oriented on runway heading of 070 degrees and reported wind was from 080 degrees at 7 knots. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot's failure to maintain directional control during landing resulting in a runway excursion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13CA438
Event ID
20131101X50450
Case number
ERA13CA438
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 10bdd4eda17024a9ebd35bca3a3cfc12fe33bda4dfd200c090c47d0588d7b40d; retrieved 2026-09-15T23:04:17.873Z.