BFO93LA086 · Cessna 182P
Cessna 182P · Accident: overrun during landing
From Elmira Corning Regional Airport (ELM) to Jolamtra Landing Area Airport (23NY)
Event
- NTSB case
- BFO93LA086
- 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
- N21137
- Operator
- Gary B Roush · private individual
- Onboard fatalities
- Unknown
- Route
- From Elmira Corning Regional Airport (ELM), Elmira, NYTo Jolamtra Landing Area Airport (23NY)
- 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 › Go-around, not performed
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS LANDING ON A 1900 FOOT LONG, WET, GRASS STRIP. ACCORDING TO HIM, THE RUNWAY HAD A STEEP UP SLOPE ON THE APPROACH END WITH TREES TO THE LEFT AND A LEFT DOWN SLOPE ON THE DEPARTURE END WITH 20 FOOT TREES NEARBY. THE PILOT STATED THAT THE RUNWAY GRASS WAS FRESHLY CUT AND RAIN HAD RECENTLY FALLEN. AS THE AIRPLANE CROSSED THE THRESHOLD AT 70 MPH WITH FULL FLAPS AND NO POWER, IT TOUCHED DOWN. THE PILOT APPLIED THE BRAKES, BUT THEY WERE INEFFECTIVE. THE AIRPLANE BEGAN TO SLIDE ON THE WET RUNWAY. REPORTEDLY, THE AIRPLANE TOUCHED DOWN ABOUT ONE THIRD OF THE WAY DOWN THE RUNWAY. IT THEN EXITED THE RUNWAY AND NOSED OVER ONTO TREES. THE PILOT STATED THAT THERE WAS NO MECHANICAL MALFUNCTION.
Probable cause
THE PILOT DID NOT ATTAIN THE PROPER TOUCHDOWN POINT AND DID NOT GO AROUND WHILE THERE WAS STILL SUFFICIENT SPEED TO DO SO. THE WET RUNWAY GRASS WAS A RELATED FACTOR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA086
- Event ID
- 20001211X12316
- Case number
- BFO93LA086
- 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: d29441877a168e26b021fe4ecf50a423ec7481ec63a0a134e93a2a8def1fa7bc; retrieved 2026-09-23T02:06:26.001Z.