FTW85FA283 · Gates Learjet 35A
Million Air Gates Learjet 35A · Accident: airframe, component or system failure during landing
From Addison Airport (ADS) to an unrecorded destination
Event
- NTSB case
- FTW85FA283
- 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
Gates Learjet 35A
- Aircraft type
- Learjet 35
- 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
- N613RR
- Operator
- Million Air
- Onboard fatalities
- Unknown
- Route
- From Addison Airport (ADS), Dallas, TXTo not recorded
- 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
- Landing · landing roll
- 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
- Company maintenance personnel › Maintenance, installation, improper
- Hydraulic system, line › Incorrect
- Landing gear, anti-skid brake system › Failure, partial
- Terrain condition › Downhill
- Terrain condition › Rough/uneven
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THIS ACFT RAN OFF THE DEPARTURE END OF THE 4001' RUNWAY FOLLOWING A NORMAL APPROACH, TOUCHDOWN AND INITIAL BRAKING. AFTER ABOUT 1000' OF NORM BRAKING, THE ACFT BEGAN A DRIFT TO THE RIGHT WHICH WAS PARTIALLY OVERCOME BY FULL LEFT RUDDER AND ASYMMETRICAL BRAKES. AFTER DEPARTING THE RUNWAY THE ACFT ENCOUNTERED DOWN SLOPING TERRAIN WHICH CAUSED THE NOSE GEAR TO COLLAPSE AND BUCKLED THE RIGHT WING. INVESTIGATION REVEALED THAT THE BRAKE LINES ON THE LEFT MLG WERE REVERSED WHICH CAUSED ERRANT COMMAND SIGNALS TO BE TRANSMITTED TO THE ANTI-SKID CONTROL UNIT DURING HEAVY BRAKE APPLICATION, NEGATING THE ANTI-SKID FUNCTION. THE LINES HAD BEEN MIS-INSTALLED DURING THE PREVIOUS BRAKE OVERHAUL. IT WAS NOTED THAT THE MAINTENANCE MANUAL DOES NOT ADDRESS THE CRITICALITY OF PROPER HOSE INSTALLATION AND THAT EITHER HOSE MAY BE INSTALLED IN THE INBD OR OTBD BRAKE HOUSING PORTS. ACFT WAS NOT EQUIPPED WITH REVERSERS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW85FA283
- Event ID
- 20001214X37123
- Case number
- FTW85FA283
- 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: 66115e96a8ce8322c3fc9047f2c5968e9a1698bf695b65882f88cdd58fdc308a; retrieved 2026-09-23T16:51:41.811Z.