FTW99LA136 · Piper PA-28-235
Piper PA-28-235 · Accident: on ground/water collision with object during takeoff
From an unrecorded airport to F54 · Arlington, TX
Event
- NTSB case
- FTW99LA136
- 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-28-235
- 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
- N9009W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo F54 · Arlington, 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 · rejected 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
- On ground/water collision with object
- 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 › Aborted takeoff, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane impacted a tree during an aborted takeoff from a 2,000-foot private grass airstrip. The private pilot stated that the takeoff roll was normal and all engine gauges and flight instruments appeared normal, except for the airspeed indicator needle, which remained between 65 and 70 knots. The pilot aborted the takeoff and maneuvered the airplane off the right side of the runway to avoid a tree. However, the airplane's right wing contacted another tree. The grass at the airstrip was between 12 and 14 inches high. The airplane's engine was test run in the airframe at various power settings, including full power. The engine operated within the manufacturer's specifications. The engine maintenance logbooks were reviewed and no record of any uncorrected maintenance discrepancies was found.
Probable cause
The delayed aborted takeoff by the pilot-in-command. Factors were the short runway, the tall grass, and the tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW99LA136
- Event ID
- 20001212X18771
- Case number
- FTW99LA136
- 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. 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: e525c432484c8cd943e7dbac10d862097f9907a045fd8bdf9b1b932c54224af6; retrieved 2026-09-22T15:19:27.031Z.