MIA98LA204 · Cessna 182P
Cessna 182P · Accident: on ground/water collision with object during landing
From W44 · Asheboro, NC to 0A1
Event
- NTSB case
- MIA98LA204
- 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 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
- N7619N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From W44 · Asheboro, NCTo 0A1
- 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
- On ground/water collision with object
- 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 › Clearance, not maintained
- Pilot in command › Directional control, not maintained
Approximate · Estimated position: the centre of Concord, NC, the place the record names. Not the accident site.
NTSB narrative
The pilot stated that after a normal approach and touchdown, the airplane veered to the right. He applied left rudder and brake to correct but not before the right wing collided with a tree. The airplane came to rest off the right side of the runway. Examination of the airplane revealed that the left wing tip was damaged caused by ground contact at a point farther down the runway than where the airplane came to rest. Also, tire marks on the runway indicate that the airplane touched down to the right of the runway centerline with the right main landing gear tire near the right edge of the runway. The airplane veered to the left then back to the right.
Probable cause
the failure of the pilot to maintain directional control and his failure to maintain wingtip clearance with trees that border the right side of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA204
- Event ID
- 20001211X10661
- Case number
- MIA98LA204
- 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: 6c95eebc92be89d66d85561ebad327003e1d9b75e93d5cbfefb6e994208b7261; retrieved 2026-09-22T17:22:34.333Z.