FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW08CA077 · Piper PA-28R-200

5 Mar 2008 · San Antonio, TX, United States

Wright Flyers Aviation Piper PA-28R-200 · Accident: hard landing

From San Antonio International Airport (KSAT) to an unrecorded destination

Report a problem

Event

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

Piper PA-28R-200

Aircraft type
Piper PA-28
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
N41517
Onboard fatalities
Unknown
Route
From San Antonio International Airport (KSAT), San Antonio, TXTo not recorded
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

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private pilot was asked to perform a power-off 180 degree accuracy landing as part of the practical test for a commercial pilot certification. The first attempt was terminated with a go-around. The second approach appeared normal according to the designated pilot examiner onboard, until approximately five seconds before touchdown. At that point the airplane rate of descent increased to approximately 1000 feet per minute and the airspeed slowed below 75 miles per hour and the airplane "dropped onto the runway." Neither the pilot nor examiner noticed any apparent damage at that time and elected to continue the flight. Upon completion of the flight the airplane was examined by maintenance for a hard landing and substantial damage was confirmed to both wings at the landing gear assembly mounts.

Probable cause

The pilot's failure to maintain airspeed during the landing flare which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW08CA077
Event ID
20080320X00343
Case number
DFW08CA077
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: 457f094a6f1160303f7823d59aca26ebcd83dff836b272929dd7c7b6ec597bc6; retrieved 2026-09-15T09:26:41.734Z.