FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW94LA254 · Boeing A75

31 Jul 1994 · Comfort, TX, United States

Boeing A75 · Accident: in flight collision with object during initial climb

From an unrecorded airport to Kerrville / Kerr County Airport at Louis Schreiner Field (ERV)

Report a problem

Event

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

Boeing A75

Aircraft type
Boeing A75
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
N60459
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Kerrville / Kerr County Airport at Louis Schreiner Field (ERV), Kerrville, 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
Initial climb
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
In flight 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 › Compensation for wind conditions, inadequate
  • Pilot in command › Propeller, improper use of

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

NTSB narrative

AFTER COMPLETING THE RUNUP THE PILOT FAILED TO PUSH THE PROPELLER LEVER TO THE FULL FORWARD POSITION. WITNESSES OBSERVED A VERY SLOW ACCELERATION AND A LONG ROLL DURING THE ATTEMPTED TAKEOFF. THE LEFT MAIN LANDING GEAR CAME OFF THE SHOULDER OF THE RUNWAY AND THE TIRE IMPACTED A RUT RESULTING IN A LOSS OF CONTROL. THE AIRPLANE COLLIDED WITH THE ROOF OF A HANGAR AND A UTILITY POLE AT THE DEPARTURE END OF THE RUNWAY. A 10 KNOT CROSSWIND EXISTED 90 DEGREES TO THE RUNWAY.

Probable cause

THE PILOT'S INADEQUATE COMPENSATION FOR THE CROSSWIND AND HIS FAILURE TO PUSH THE PROPELLER LEVER FULL FORWARD. FACTORS WERE THE CROSSWIND AND THE PILOT'S FAILURE TO FOLLOW THE BEFORE TAKEOFF CHECKLIST.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW94LA254
Event ID
20001206X01761
Case number
FTW94LA254
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: edf82c86a5587f7b1febc0b657b92b97a53a5d8060ec24357809ed39912f3593; retrieved 2026-09-21T13:44:14.096Z.