FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10CA069 · Paradise USA LLC PARADISE P-1 SLSA LW

17 Nov 2009 · Plant City, FL, United States

Paradise USA LLC PARADISE P-1 SLSA LW · Accident: hard landing

From Plant City Municipal Airport (PCM) to Plant City Municipal Airport (PCM)

Report a problem

Event

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

Paradise USA LLC PARADISE P-1 SLSA LW

Aircraft type
Paradise P-1
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
N917ZZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Plant City Municipal Airport (PCM), Plant City, FLTo Plant City Municipal Airport (PCM), Plant City, 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
Landing · flare/touchdown
Defining eventThe 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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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 of the special light sport airplane had completed an uneventful full-stop landing and was conducting a second full-stop landing on the asphalt runway. During the landing flare, the left wing dropped slightly and the airplane landed hard. The left main landing gear separated and the airplane came to rest on grass after veering off the left side of the runway. The airplane incurred damage to to the horizontal stabilator. The pilot stated that he did not experience any mechanical malfunctions during the accident. The wind was reported as calm about the time of the accident.

Probable cause

The pilot's improper flare while landing, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10CA069
Event ID
20091120X82236
Case number
ERA10CA069
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: e54ff64eca402bdea8e844dd71be4543a63060ddfcce8e263d903ded59b926d4; retrieved 2026-09-15T13:30:25.269Z.