DFW07CA182 · Cessna 182
Cessna 182 · Accident: overrun during landing
From N53 · E Stroudburg, PA to P32 · Husky Haven, PA
Event
- NTSB case
- DFW07CA182
- 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 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
- N71162
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From N53 · E Stroudburg, PATo P32 · Husky Haven, PA
- 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 › Proper touchdown point, not attained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The single-engine airplane overran the departure end of runway 10 while landing on a 1,900-foot long, by 100-foot wide grass airstrip. The 1,240-hour commercial pilot reported on NTSB Form 6120.1 that he flew the airplane at "70 knots, and upon touchdown, didn't get on brakes right away." The pilot added that "when I did it was too late, I slowed to about 10 MPH and ran-off the runway, down an embankment, and flipped-over." In the recommendation section marked "How could this accident have been prevented?" the pilot stated "I should have landed at '60' or '65' and got on the brakes right away." The pilot was able to egress the aircraft unassisted. No mechanical anomalies or discrepancies were reported. Two individuals witnessed the landing at the airstrip. One eyewitness recalled that the aircraft appeared to be traveling "fast" and touched down near "half the length of the runway" or approximately 950 feet. Another eyewitness reported that the airplane appeared to touch down smoothly, but at a fast rate of speed. This eyewitness continued to observe the roll-out noticing that the aircraft did not appear to decelerate after touching down and he observed the airplane overrunning the departure end of the runway into the terrain. The airfield manager described the condition of the grass airstrip as "well-maintained and dry" at the time of the mishap. The winds at the time of the accident were reported from 330 degrees at 11, gusting to 18 knots.
Probable cause
The pilot's failure to attain the proper touchdown point. A contributing factor was the prevailing tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07CA182
- Event ID
- 20071106X01742
- Case number
- DFW07CA182
- 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, coordinates. 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: c2dabde8577e5bf3c232fc02e216c935f2152b4f1d01031c0b5136a464981bd1; retrieved 2026-09-22T03:31:56.033Z.