FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW03LA038 · Agusta A109E

8 Nov 2002 · Fort Worth, TX, United States

Agusta A109E · Accident: loss of control in flight during takeoff

From Harris Hospital Heliport (TE30) to Grand Prairie Municipal Airport (GPM)

Report a problem

Event

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

Agusta A109E

Aircraft type
Agusta A109
Category
Helicopter
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
N142CF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Harris Hospital Heliport (TE30), Fort Worth, TXTo Grand Prairie Municipal Airport (GPM), Grand Prairie, TX
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
Takeoff
First occurrenceThe 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
Loss of control in flight
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

  • Pilot in command › Throttle/power control, improper

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

NTSB narrative

After landing on the helipad, the pilot reduced the throttles to flight idle. The pilot was then going to demonstrate to the flight crew how the helicopter could taxi and perform a running takeoff. The pilot initiated the takeoff roll, added collective, and realized the engines were not at 100 percent power. Subsequently, the helicopter became airborne, departed the heliport and came to rest on the roof of a lower level parking garage. In an interview, the pilot reported that "he attempted a rolling take-off...with an incorrect power setting (selection switch) which resulted in an emergency landing on the roof of an adjacent automobile parking garage due to insufficient engine power to maintain flight." The pilot had accumulated approximately 6,500 total helicopter flight hours, with 3,100 flight hours as a flight instructor in helicopters, and 25 total hours in the same make and model as the accident helicopter.

Probable cause

The pilot's attempted running takeoff with the power controls in the improper position.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW03LA038
Event ID
20021114X05468
Case number
FTW03LA038
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 7e2cacb149620591c138afde1de9f6edc8adb24f3009b7feea54fcf2f2e0d24a; retrieved 2026-09-22T09:58:07.180Z.