FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL03LA005 · Cessna 172

17 Oct 2002 · Opa Locka, FL, United States

Cessna 172 · Accident: loss of control on ground/water during takeoff

From Miami-Opa Locka Executive Airport (OPF) to an unrecorded destination

Report a problem

Event

NTSB case
ATL03LA005
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 172

Aircraft type
Cessna 172
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
N903WA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Miami-Opa Locka Executive Airport (OPF), Opa Locka, FLTo not recorded
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
Takeoff
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(cfi) › Aircraft preflight, inadequate
  • Pilot in command(cfi) › Wrong runway, selected
  • Weather condition › Tailwind

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

NTSB narrative

The certified flight instructor (CFI), who was flying the airplane, and the student pilot were conducting touch-and-go landings to runway 27. They had completed three touch-and-go procedures and were on the fourth takeoff when an updraft lifted the airplane off the runway. The student pilot reported that the airplane ballooned into the air and came down "hard" on to the runway. The airplane also collided with a runway light and the right wing tip was also damaged. The CFI did not report a mechanical problem with the airplane. The nearest weather reporting facility, Fort Lauderdale, Florida, reported prevailing winds from 050 degrees at 14 knots at the time of the accident. The CFI obtained weather information from Opa Locka Automatic Terminal Information System (ATIS)

Probable cause

The pilot' inadequate evaluation of weather information, and the selection of the wrong runway that resulted in an attempted takeoff with a tailwind and the subsequent loss of control during takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL03LA005
Event ID
20021022X05365
Case number
ATL03LA005
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: ab138e4a2375ffa1f5350eba6cd2e2367fc5fac5515307bb893b179d56346dcb; retrieved 2026-09-22T10:04:04.856Z.