FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL06CA081 · Piper PA28-140

18 May 2006 · Murfreesboro, TN, United States

Maxair Piper PA28-140 · Accident: loss of control on ground/water during landing

From Smyrna Airport (KMQY) to City of Murfreesboro Airport (KMBT)

Report a problem

Event

NTSB case
ATL06CA081
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 PA28-140

Aircraft type
Piper PA28
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
N9902W
Operator
Maxair
Onboard fatalities
Unknown
Route
From Smyrna Airport (KMQY), Smyrna, TNTo City of Murfreesboro Airport (KMBT), Murphreesboro, TN
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

  • 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 student pilot stated that he departed Smyrna, Tennessee, and flew direct to Murphreesboro, Tennessee. Upon arrival he listened to the Airport Terminal Information System information and observed the wind sock which indicated a right crosswind. The student pilot overflew the airport at midfield, descended, entered left traffic for runway 18, completed the before landing checklist, lowered flaps to one notch, and turned on the base leg. The student pilot turned the airplane on final approach, reduced airspeed, lowered flaps to the second notch, and entered right aileron for the crosswind correction. The power was reduced 30 feet from his intended touchdown point. The airplane touched down on the runway, and the cross wind correction was removed on landing roll out. The airplane veered to the right, the student pilot applied left rudder, and lost directional control of the airplane. The airplane turned 90-degrees, slid sideways off the side of the runway, and collided with a ditch coming to a complete stop. The student pilot stated that he did not experience any mechanical problems with the airplane before the accident, and he just lost directional control of the airplane.

Probable cause

The student pilot's failure to maintain directional control during landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL06CA081
Event ID
20060623X00809
Case number
ATL06CA081
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: ac95e42a21f68c2749732558bde7f5c0fea598f14d1851121dcfaf28acdbbe44; retrieved 2026-09-22T04:55:00.883Z.