FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10CA467 · Sport Plane Dynamics LLC LIGHTNING

22 Sept 2010 · Glendale, AZ, United States

Sport Plane Dynamics LLC LIGHTNING · Accident: hard landing

From Glendale Municipal Airport (GEU) to Glendale Municipal Airport (GEU)

Report a problem

Event

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

Sport Plane Dynamics LLC LIGHTNING

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
N121L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Glendale Municipal Airport (GEU), Glendale, AZTo Glendale Municipal Airport (GEU), Glendale, AZ
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 › Action/decision

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

NTSB narrative

The pilot-owner completed building his airplane and then performed a test flight with a pilot-rated passenger on board. The pilot-owner reported that the passenger was on board to assist him in becoming acquainted with the airplane's flying characteristics because the passenger had flying experience in somewhat similar airplanes. The passenger stated that after various maneuvers were performed, the pilot-owner attempted to land. Following the landing flare the pilot lost control of the airplane, it bounced several times, veered off the runway, and it came to rest in a nose low upright attitude. The airplane's undercarriage partially collapsed, both ailerons and the rudder were bent, and the airplane was substantially damaged. Airport personnel reported that the wind speed was 3 knots. No mechanical failures or malfunctions were reported.

Probable cause

The pilot's improper flare, which resulted in a bounced landing and loss of directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10CA467
Event ID
20100922X32537
Case number
WPR10CA467
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: 48c957edeb873ce9bde596008ed78f4656dc96e609458d0ac908bd6db9f7e59f; retrieved 2026-09-15T15:19:09.055Z.