FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW96TA195 · Rockwell NA-265-80

1 May 1996 · Albuquerque, NM, United States

Rockwell NA-265-80 · Accident: airframe, component or system failure during takeoff

From Albuquerque International Sunport (ABQ) to Santa Fe Municipal Airport (SAF)

Report a problem

Event

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

Rockwell NA-265-80

Aircraft type
Rockwell NA-265
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
N773W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Albuquerque International Sunport (ABQ)To Santa Fe Municipal Airport (SAF), Santa Fe, NM
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 · roll/run
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
Airframe, component or system failure
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

  • Landing gear, tire › Failure
  • Landing gear, tire › Fatigue
  • Landing gear, tire › Pressure too low

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

NTSB narrative

The captain was taking off on runway 21 with the wind from 330 degrees at 6 knots. After the airplane had attained about 120 knots and had traversed about half the 10,000 foot runway, the captain aborted the takeoff, when he heard a loud noise and felt a severe vibration. Subsequently, the airplane angled off the departure end of the runway and encountered soft terrain. It came to rest about 300 feet beyond the end of the runway with the nose landing gear collapsed. According to a tire analysis report, the left outboard tire failed in fatigue, followed by the left inboard tire, 'as the result of operation in an overdeflected condition.' The report stated, 'Over-deflection is caused by operating the tire overloaded or underinflated.'

Probable cause

overdeflection of the left outboard main landing gear tire, probably due to underinflation and inadequate inspection, which resulted in fatigue failure of the left outboard tire and subsequent failure of the left inboard tire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW96TA195
Event ID
20001208X05780
Case number
FTW96TA195
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1996-05-02.
  • API snapshot SHA-256: 6d04a5a7ca4cfa3352e682706e12ebbb5e049907e435d75180b8536706c58646; retrieved 2026-09-22T22:32:45.944Z.