ERA09CA301 · Cessna 172N
Cessna 172N · Accident: runway excursion during landing
From Wilkes Barre Wyoming Valley Airport (WBW) to Skyhaven Airport (76N)
Event
- NTSB case
- ERA09CA301
- 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 172N
- Aircraft type
- Cessna 172
- 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
- N9492E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wilkes Barre Wyoming Valley Airport (WBW), Wilkes-Barre, PATo Skyhaven Airport (76N), Tunkhannock, 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
- 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
- Runway excursion
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he checked the wind sock, then flew a "standard" traffic pattern at a final approach speed of 70 knots and 20-degrees flaps. He subsequently landed the airplane on runway 1, a 2,007-foot-long runway, “a few hundred feet past the threshold,” and it "seem[ed] as though [he] had a wind shift which became a tailwind." The pilot's subsequent application of brakes did not slow the airplane and during an attempt to turn off the runway, the airplane "would not steer." The airplane overran the end of the runway, went down a 10-foot embankment, nosed over, and sustained damage to the vertical stabilizer and left wing. Winds, recorded at an airport 15 miles to the southeast about the time of the accident, were from 230 degrees true at 9 knots. The pilot did not report any mechanical anomalies with the airplane.
Probable cause
The pilot's failure to attain the proper touchdown point while landing with a tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA301
- Event ID
- 20090522X40533
- Case number
- ERA09CA301
- 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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: c8176812f830698f7fb076ff40cbdcb2f019b0670f25c481701ec788f7b2ab2a; retrieved 2026-09-15T11:08:18.557Z.