FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12LA384 · Cessna 182R

31 Aug 2012 · St. Johns, AZ, United States

Cessna 182R · Accident: runway excursion during landing

From Dalhart Municipal Airport (DHT) to St Johns Industrial Air Park (SJN)

Report a problem

Event

NTSB case
WPR12LA384
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 182R

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
N5458N
Operator
Bruce D. Lisle · private individual
Onboard fatalities
Unknown
Route
From Dalhart Municipal Airport (DHT), Dalhart, TXTo St Johns Industrial Air Park (SJN), St. Johns, AZ
Aircraft age
About 32 years (built 1980)
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

The pilot reported that the airplane was high and fast on final approach for landing, so he lowered the flaps to 40 degrees and raised the nose to slow down. The pilot then decided to go around, so he applied full power and raised the flaps to 30 degrees. The airplane began to climb, but then it started descending. The pilot reduced the engine power, landed the airplane, and applied heavy braking. The airplane subsequently overran the end of the runway and went through the perimeter fence. After he exited the airplane, the pilot found the flaps fully retracted. The airplane's Pilot Operating Handbook stated that go-arounds should be performed with the flaps at 20 degrees. Further, the pilot should have performed a go-around when he first noticed that the airplane was too high and fast on the final approach.

Probable cause

The pilot’s delay in executing a go-around, which resulted in a runway overrun. Contributing to the accident were the pilot’s failure to establish the proper glidepath and airspeed on final approach and his improper use of flaps during the go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12LA384
Event ID
20120901X25532
Case number
WPR12LA384
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: eb1aa55df791429d9f63c667dad67cd50ca448dc9cdbf2e3d7f3c8ebd0dcccd8; retrieved 2026-09-15T19:38:15.085Z.