FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA98LA072 · Cessna 172

6 Feb 1998 · Daytona Beach, FL, United States

Embry Riddle Aeronautical Univ Cessna 172 · Accident: loss of control on ground/water during landing

From Melbourne Orlando International Airport (MLB) to Daytona Beach International Airport (DAB)

Report a problem

Event

NTSB case
MIA98LA072
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 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
N406ER
Onboard fatalities
Unknown
Route
From Melbourne Orlando International Airport (MLB), Melbourne, FLTo Daytona Beach International Airport (DAB)
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 › Aileron, improper use of
  • Pilot in command › Brakes(normal), improper use of

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated he made a landing with a crosswind from the right. No aileron correction was used. On landing rollout the airplane started to drift to the right, the pilot applied left rudder with negative results. The airplane continued to the right off the right side of the runway. He observed a taxiway sign and applied right rudder, and the airplane collided with the sign. Examination of the brakes, flight controls and nosewheel steering revealed no evidence of a precrash mechanical failure or malfunction. Examination of the right main landing gear revealed a scuff mark. Examination of the runway surface revealed a skid mark veering to the right of the centerline which was consistent with the damage noted on the right main landing gear.

Probable cause

The pilot's improper use of ailerons and brakes on landing rollout.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA98LA072
Event ID
20001211X09582
Case number
MIA98LA072
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. 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: 864a8cab2c52367432c1a9eeda3c1b6831c05f69a6ead466d14c6d176c42797c; retrieved 2026-09-22T18:03:03.567Z.