FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA236 · Cessna 140

10 May 2009 · Mesquite, NV, United States

Cessna 140 · Accident: system/component malfunction/failure (non-power) during landing

From Mesquite Airport (67L) to Mesquite Airport (67L)

Report a problem

Event

NTSB case
WPR09LA236
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 140

Aircraft type
Cessna 140
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
N73017
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mesquite Airport (67L), Mesquite, NVTo Mesquite Airport (67L), Mesquite, NV
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
System/component malfunction/failure (non-power)
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
  • Aircraft › Aircraft systems

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that he made a normal landing on the runway. During rollout, he felt a vibration coming from the landing gear. When he exited the runway, the airplane turned abruptly to the left, as if the left brake had locked up. The uncommanded sharp left turn resulted in the airplane exiting the pavement and impacting a cement culvert. The examination of the runway revealed witness marks consistent with a locked left wheel brake. An examination of the airplane's left wheel assembly revealed that the tire rotated freely. No external evidence of brake failure was found. The reason for the intermittent anomaly associated with the brake assembly or cylinder was not determined.

Probable cause

The pilot's loss of directional control during landing resulting from binding of the left wheel's brake actuating system for an undetermined reason.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA236
Event ID
20090511X24102
Case number
WPR09LA236
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. 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: c729127a8aed2fe0c55a5f1c98c10dd067899880b166ce72ac242135ad810eeb; retrieved 2026-09-15T11:02:04.019Z.