NYC99LA162 · Cessna 182
Cessna 182 · Accident: overrun during landing
From Roanoke–Blacksburg Regional Airport (ROA) to W90
Event
- NTSB case
- NYC99LA162
- 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 182
- 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
- N5481B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Roanoke–Blacksburg Regional Airport (ROA), Roanoke, VATo W90
- 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
- Overrun
- 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 › Distance/speed, misjudged
- Pilot in command › Go-around, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before departing, the pilot referred to the Airport Facilities Directory to check the runway length at his destination. On arrival, he checked the windsock and determined that there was a direct crosswind, and decided to land on Runway 34, a 3,164-foot long runway. The pilot intentionally planned for a higher approach because of the 'limited light, and terrain.' As the airplane landed on Runway 34, about 60-65 MPH, with 30 degrees of flaps, the pilot noticed the gas pumps and hangers located on the northwest side of the airport abeam the airplane to his left. The airplane bounced once, began to float, and touched down again with about 240 feet of runway remaining. The pilot attempted to use maximum baking, but could not stop. The fuel pumps and hangers were located in a position that corresponded to about 800 feet remaining on Runway 34.
Probable cause
The pilot's misjudgment of distance/speed, also causal was his failure to execute a go-around. Contributing factors were the night conditions and the tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99LA162
- Event ID
- 20001212X19106
- Case number
- NYC99LA162
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1999-06-29.
- API snapshot SHA-256: a2d4b607f3633092ba8324ef9478c2571f33d146821d9f98ece79dbbd30ceb91; retrieved 2026-09-22T14:44:03.961Z.