FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA97LA116 · Rosen ONE DESIGN

7 Apr 1997 · Lakeland, FL, United States

Rosen ONE DESIGN · Accident: hard landing

From 55J · FERNANDO BEACH, FL to Lakeland Linder International Airport (LAL)

Report a problem

Event

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

Rosen ONE DESIGN

Aircraft type
Rosen ONE DESIGN
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
N213JR
Operator
Jack M. Rosen · private individual
Onboard fatalities
Unknown
Route
From 55J · FERNANDO BEACH, FLTo Lakeland Linder International Airport (LAL)
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 · flare/touchdown
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
Hard landing
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 › Recovery from bounced landing, improper

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

NTSB narrative

The airplane was observed making a crosswind landing. As the pilot started his round out/flare, the nose pitched up and the airplane banked to the left. The airplane touched down on the left main gear and tailwheel. The airplane started to porpoise and bounced four times before the pilot initiated a go-around. The tailwheel broke off on the third bounce. The witness called the advisory tower, informed them of the situation, and asked them to relay the information to the control tower, so they could inform the pilot. The pilot made a low pass by the tower to confirm the damage. A short time later the pilot informed the tower that his windshield was obscured by oil. He made another approach which resulted in a go-around. He remained in closed traffic and made an emergency landing to the grass.

Probable cause

The pilot's improper recovery from a bounced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA97LA116
Event ID
20001208X07773
Case number
MIA97LA116
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: 6ed463e1b7900d2aaccdba3356990974aef16d4d634f5dcdd8626957df232d9f; retrieved 2026-09-22T19:59:53.405Z.