FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09LA544 · Celier Aviation XENON RST

25 Sept 2009 · Mount Pleasant, SC, United States

Celier Aviation XENON RST · Accident during initial climb

From Raven's Run Airport (SC65) to Raven's Run Airport (SC65)

Report a problem

Event

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

Celier Aviation XENON RST

Aircraft type
Celier XENON RST
Category
Gyroplane
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
N4462J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Raven's Run Airport (SC65), Mount Pleasant, SCTo Raven's Run Airport (SC65), Mount Pleasant, SC
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
Initial climb
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
Miscellaneous/other
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

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

NTSB narrative

The pilot stated that the gyroplane took off about 1,200 feet from the departure end of runway 15 and experienced a "loss of lift" when it was approximately 30 feet above the ground. The pilot "lowered the nose to increase airspeed to increase lift," but the gyroplane continued to descend. With no runway available, the gyroplane landed "flat" into a lake, and after exiting the pilot and passenger swam to shore. No preaccident mechanical anomalies were noted with the gyroplane, which was about 90 pounds below maximum gross weight at takeoff. Winds were from 190 degrees true at 5 knots, and temperature at the time was 32 degrees C. The extent to which the combination of high gross weight and high ambient temperature may have affected the flight was not determined.

Probable cause

The gyroplane's inadequate climb performance for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09LA544
Event ID
20091001X13535
Case number
ERA09LA544
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. 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: b8dad07237627d74ec9404dafc8a016f081769c809ac1ea6bc385683f40a82ef; retrieved 2026-09-15T13:21:59.503Z.