FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05LA012 · Rockwell 112A

24 Oct 2004 · Tampa, FL, United States Narrative disagrees

Rockwell 112A · Accident: overrun during takeoff

From Peter O Knight Airport (KTPF) to Lakeland Linder International Airport (KLAL)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Rockwell 112A

Aircraft type
Rockwell 112
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
N112ND
Operator
Unknown
Onboard fatalities
Unknown
Route
From Peter O Knight Airport (KTPF), Tampa, FLTo Lakeland Linder International Airport (KLAL), Lakeland, FL
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 · rejected 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
Overrun
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 › Flaps, improper use of

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 stated the preflight, start, taxi, and run-up, were conducted in accordance with the aircraft checklist prior to the takeoff roll. Upon reaching the rotation speed, backpressure was applied to the control yoke when the airplane failed to respond to the control inputs, she made the decision to abort the takeoff. During the aborted takeoff the airplane traveled off the paved runway surface. Upon contact with the grass at the end of runway 03 the airplane skid sideways towards the seawall. The airplane went over the seawall and became submerged in the water. The non-pilot passenger stated she was seated to the right of the pilot at the time of accident. The pilot tried to stop, but the airplane skidded off the runway and over the seawall. She and the pilot exited the airplane without assistance. A witness stated to the local police that she was driving northeast on Davis boulevard paralleling runway 03 at the Peter O'Knight Airport, when she observed the accident airplane on the takeoff roll. She observed the airplane going "very fast" down the runway. Past the point she thought it should takeoff, it veered to the right, traveled off the runway and went into the water. She was unsure if the airplanes nose rose off the ground or not. She stated she never heard the engine turn off. The FAA inspector who responded to the accident scene stated that the flap indicator on the instrument panel was positioned near the zero-degree mark.The flight controls were checked and they operated normal with no binding. At the time the airplane was pulled from the water the flap configuration was not at the required 10-degrees for normal takeoff. The 112A flight manual requires the pilot to use 10-degrees of flaps for normal takeoff. The aircraft was departing from runway 03, a published 3,400-foot-long runway.

Probable cause

The pilot's failure to properly set flaps for takeoff which resulted in the aborted takeoff and subsequent impact with water during an overrun of the runway and seawall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05LA012
Event ID
20041105X01768
Case number
MIA05LA012
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: f814f67cc773416dbcf9c9b3e01651d600b06d4397ebb3d8c0a17e9d1000d6f7; retrieved 2026-09-22T06:34:44.197Z.