FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DCA09FA028 · General Atomics MQ-9

19 Feb 2009 · Sierra Vista, AZ, United States

General Atomics MQ-9 · Accident: hard landing

From Sierra Vista Municipal Airport / Libby Army Air Field (KFHU) to Sierra Vista Municipal Airport / Libby Army Air Field (KFHU)

Report a problem

Event

NTSB case
DCA09FA028
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
Government
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

General Atomics MQ-9

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
CBP-108
Onboard fatalities
Unknown
Route
From Sierra Vista Municipal Airport / Libby Army Air Field (KFHU), Sierra Vista, AZTo Sierra Vista Municipal Airport / Libby Army Air Field (KFHU), Sierra Vista, 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
Public Aircraft
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
  • Personnel issues › Task performance

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

NTSB narrative

At the time of the accident the flight was operating as a Launch Recovery Element training mission, performing touch-and-go landings on runway 26. Customs and Border Protection had resumed pilot training following a Federal Aviation Administration-imposed suspension as a result of an accident 2 days prior. The accident landing was the seventh of eight planned landings. As the student pilot rotated the aircraft into the landing flare about six feet above the touchdown zone, a tailwind of approximately 9 knots was recorded. The instructor told the student to increase the pitch to arrest the descent rate and increase power to begin a go-around. However, the aircraft touched down hard on the main gear and lower vertical stabilizer and porpoised a number of times. The instructor then took over, executing a go-around and landing with no further incident. The aircraft sustained damage to the propeller, left main landing gear, vertical fin and the lower cowl. There was no evidence of any preexisting anomalies with the aircraft.

Probable cause

The student pilot's improper flare while landing with a tailwind and the instructor pilot's delayed response.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA09FA028
Event ID
20090220X64906
Case number
DCA09FA028
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: 1d91fcd0dc09c8d65583b6e2b30689f7cddc3754f11daa52ce1f867fc208c8e7; retrieved 2026-09-15T10:46:02.250Z.