Simmons Airlines ATR 72-212 incident
ATR 72-212 · Incident: airframe, component or system failure while taxiing
From Lubbock Preston Smith International Airport (LBB) to Dallas Fort Worth International Airport (DFW)
Event
- NTSB case
- FTW95IA096
- 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
- Incident
- 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
- Airline
- 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
ATR 72-212
- Aircraft type
- ATR 72
- 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
- N408AT
- Operator
- Simmons Airlines
- Onboard fatalities
- Unknown
- Route
- From Lubbock Preston Smith International Airport (LBB), Lubbock, TXTo Dallas Fort Worth International Airport (DFW), DFW AIRPORT, 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 121: Air Carrier
- 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
- Taxi · from runway
- 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
- Minor
Cause areas
- Landing gear, normal brake system › Activated
- Landing gear, normal brake system › Uncommanded
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THE CREW EXPERIENCED AN UNCOMMANDED BRAKE APPLICATION TO BOTH TIRES ON THE RIGHT MAIN LANDING GEAR ABOUT FIVE SECONDS AFTER TOUCHDOWN. THE PILOT WAS ABLE TO MAINTAIN DIRECTIONAL CONTROL OF THE AIRPLANE BY USING LEFT RUDDER AND NOSE WHEEL STEERING. WHILE TAXIING TO THE GATE THE HOT BRAKE TEMPERATURE WARNING LIGHT FOR THE RIGHT MAIN LANDING GEAR ILLUMINATED. A FIRE WAS OBSERVED IN THE VICINITY OF THE RIGHT LANDING GEAR AND THE CREW INITIATED AN EMERGENCY EVACUATION ON THE TAXIWAY. NO ANOMALIES WERE FOUND WITH ANY OF THE LANDING GEAR/BRAKE SYSTEM COMPONENTS. THE REASON FOR THE UNCOMMANDED BRAKE APPLICATION COULD NOT BE DETERMINED.
Probable cause
THE UNCOMMANDED ACTIVATION OF THE BRAKE SYSTEM ON THE RIGHT MAIN LANDING GEAR FOR UNDETERMINED REASON.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95IA096
- Event ID
- 20001207X02856
- Case number
- FTW95IA096
- 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: 87cf4d659ba839cadc30a4e6d3080e400bfb7d9b610d6717a6adf73cd5b921c5; retrieved 2026-09-18T18:04:20.107Z.