FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI04LA048 · Piper PA-28R-200

21 Dec 2003 · Mountain Grove, MO, United States

Piper PA-28R-200 · Accident: loss of control on ground/water during landing

From Mountain Grove Memorial Airport (1MO) to Mountain Grove Memorial Airport (1MO)

Report a problem

Event

NTSB case
CHI04LA048
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

Piper PA-28R-200

Aircraft type
Piper PA-28
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
N56598
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mountain Grove Memorial Airport (1MO), Mountain Grove, MOTo Mountain Grove Memorial Airport (1MO), Mountain Grove, MO
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
First occurrenceThe 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
Loss of control on ground/water
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

  • Landing gear, tire › Failure
  • Pilot in command › Brakes(normal), improper use of
  • Pilot in command › Directional control, not maintained

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

NTSB narrative

The airplane was substantially damaged during landing when it departed the runway pavement and encountered a ditch. The pilot estimated the wind during the accident flight at five knots or less. He noted that the pre-takeoff brake check was normal and the takeoff was uneventful. The pilot stated that upon landing the aircraft began pulling to the left. He reported that he applied full right rudder and right brake. However, the aircraft began tracking toward the left side of the runway and subsequently departed the pavement. The aircraft encountered a small ditch and the left main landing gear collapsed. A local pilot reported observing the aircraft's approach and thought that it was slightly high and fast. She also recalled hearing one, louder than normal "chirp" of the tires on the runway during landing touchdown, leading her to think the pilot had made a "hard 3 point landing." The president of the flying club from which the pilot had rented the aircraft reported having a conversation concerning the accident with the pilot. He commented to the pilot that, during a crosswind landing situation in the model aircraft involved, it "would be easy to push with the toes to lock the brake." The pilot reportedly responded that "that was probably the case." A post-accident inspection revealed the left main landing gear had collapsed and damaged the left wing. The left main tire had a hole worn through the tread area. The brake system on the left main landing gear was examined. No anomalies consistent with a pre-impact failure were observed. The runway exhibited tire marks beginning approximately 1,400 feet from the threshold and continuing, virtually uninterrupted, to the point the aircraft departed the pavement. The marks in the grass continued from that point to the aircraft's resting position in the ditch. The initial skid mark was associated with the left main landing gear. It continued approximately 275 feet and paralleled the runway centerline. The mark was characterized by a single, continuous line with the exception of two short breaks. The skid mark produced by the left main gear tire changed to a set of two parallel marks characteristic of a flat tire. At this point, the mark indicated that the aircraft began tracking toward the left side of the runway and was continuous until it left the pavement. A single, continuous skid mark associated with the right main landing gear tire began about the time the aircraft started tracking to the left.

Probable cause

Improper use of the brakes during landing by the pilot, resulting in failure of the left main landing gear tire and a loss of directional control. Contributing factors were the failure of the main landing gear, as well as the grass and the ditch adjacent to the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA048
Event ID
20040106X00019
Case number
CHI04LA048
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 73175def7084a9315154de8d69715162eadd57cc0d38fe14308d0eca4da317a6; retrieved 2026-09-22T08:03:54.646Z.