MIA08CA182 · Cessna 172K
Cherry Ridge Airport Flying Club Cessna 172K · Accident: runway excursion during landing
From Cherry Ridge Airport (N30) to Skyhaven Airport (76N)
Event
- NTSB case
- MIA08CA182
- 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 172K
- 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
- N79210
- Operator
- Cherry Ridge Airport Flying Club
- Onboard fatalities
- Unknown
- Route
- From Cherry Ridge Airport (N30), Honesdale, 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the Cessna 172K stated that he entered the pattern for runway 1, a 2007-foot-long, 50-foot-wide, asphalt runway. His traffic pattern altitude was 200 feet higher than the required 1,500 feet. He performed a slip to lose the excess altitude and establish an 80-mph descent on a downwind leg, with 10 degrees of flap extension. The pilot added another 10 degrees of flaps, reduced the throttle to 1,300 rpm, and turned onto a base leg. The airplane's speed remained at 80 mph, instead of decreasing to the 75 mph speed he was trying to attain. Although his speed was still higher than the speed he wanted, he turned to final and overshot the runway "numbers." He added, "the plane was traveling too fast to make the turn at the end of the runway." Consequently, he "ran off the end of the runway into an embankment." The pilot did not report any mechanical or flight control anomalies prior to the accident.
Probable cause
The pilot's improper airspeed while landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA08CA182
- Event ID
- 20081003X42133
- Case number
- MIA08CA182
- 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 local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ef7fcb7070e775ad4ea007040fb1ecf27860fb2e6c785311b73e3b21e82b5e71; retrieved 2026-09-15T10:20:47.799Z.