WPR14CA155 · Cessna 172M M
Cessna 172M M · Accident: runway excursion during landing
From Skagit Regional Airport (BVS) to Anacortes Airport (74S)
Event
- NTSB case
- WPR14CA155
- 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 172M M
- 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
- N19982
- Operator
- Jamison Vernon Leo
- Onboard fatalities
- Unknown
- Route
- From Skagit Regional Airport (BVS), Burlington, WATo Anacortes Airport (74S), Anacortes, WA
- Aircraft age
- About 42 years (built 1972)
- 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 reported that during the landing and rollout, the airplane was going faster than he wanted at his normal turnoff point on the runway so he continued to the next turnoff. While turning, he applied the brakes, raised the flaps, and pushed in the carburetor heat control. At that time, he realized that the airplane was not stopping so he applied more braking, but the airplane did not slow down or stop. Before he could move his feet higher onto the toe brakes, the airplane departed the runway surface onto bumpy ground, headed over a bank, and nosed over. The wings, vertical stabilizer and rudder were substantially damaged. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's improper application of brakes during the landing roll resulted in a runway excursion and nose over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14CA155
- Event ID
- 20140402X32616
- Case number
- WPR14CA155
- 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: 55f69122acd099f9901db2cdb2763bd51d7c8d5d6dd63b28142b49ee1c3c5ba4; retrieved 2026-09-15T23:28:20.601Z.