CEN26LA040 · Cessna 180K
Cessna 180K · Accident on approach
From Banks Ranch Airport (62AR) to Gastons Airport (3M0)
Event
- NTSB case
- CEN26LA040
- 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
- 0
- 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 180K
- Aircraft type
- Cessna 180
- 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
- N2697K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Banks Ranch Airport (62AR), Busch, ARTo Gastons Airport (3M0), Lakeview, AR
- Aircraft age
- About 46 years (built 1979)
- 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
- Approach · VFR pattern final
- 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
- Miscellaneous/other
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During landing, the pilot stated he had difficulty seeing due to the sun in his eyes. He thought his visibility would improve as his altitude decreased but it did not. The airplane floated longer in the flare than anticipated. The pilot elected to land, use aggressive braking, and if necessary, cross a road into an open area that could be used as an overrun. During the landing roll he was unable to use the open area to stop beyond the end of the runway because there were two cars on the road which the pilot turned sharply to the left to avoid. During the turn, the left wheel assembly separated from the airplane and the landing gear strut dug into the ground. The airplane was substantially damaged when the left wing struck the ground bending the spar outboard of the wing strut. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s decision to continue an approach that resulted in a long landing and inability to stop prior to the end of the runway. Contributing to the accident were the light conditions and a road with vehicles on it immediately adjacent to the end of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN26LA040
- Event ID
- 20251110201971
- Case number
- CEN26LA040
- 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, coordinates, cause areas. 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: 5e5d5ceedd545e700b22d8ac8beafb71b341e70abbb701b950011af4680df706; retrieved 2026-09-16T20:31:51.266Z.