Frontier Airlines Flight 776
Boeing 737-200RS · Incident: airframe, component or system failure during initial climb
From Salt Lake City International Airport (SLC) to Denver International Airport (DEN)
Event
- NTSB case
- FTW97IA363
- 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
Boeing 737-200RS
- Aircraft type
- Boeing 737
- 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
- N205AU
- Operator
- Frontier Airlines
- Onboard fatalities
- Unknown
- Route
- From Salt Lake City International Airport (SLC)To Denver International Airport (DEN), Denver, CO
- 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
- 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
- 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
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight crew said that when they raised the landing gear handle after takeoff, the master caution light illuminated as the result of the loss of 'A' system hydraulics. The captain declared an 'emergency' and preparations were made to land on runway 16L (12,004 feet by 150 feet). The first officer conducted the landing using 15 degrees of flaps and a landing speed of 140 knots. When he deployed the thrust reversers, the left thrust reverser malfunctioned resulting in asymmetrical braking thrust. The airplane's operations manual indicated that with the loss of 'A' hydraulic system and an airplane weight of 89,600 pounds, a landing speed of 156 knots should be used. Directional control during the landing roll would have been accomplished using rudder and differential braking because nose wheel steering would have been inoperable. The captain reported to the FAA Inspector and Frontier Airlines officials that during the landing roll, he took control of the airplane. Photographs taken at the incident scene indicated that after 8,000 feet of runway was used, the airplane's tire skid marks became significantly darker, with right two skid marks darker than the left two.
Probable cause
The captain's failure to maintain directional control during landing roll. Factors were the loss of hydraulic pressure in the 'A' hydraulic system, the thrust reverser failure on the number one engine, and flight crew coordination not being maintained.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW97IA363
- Event ID
- 20001208X08834
- Case number
- FTW97IA363
- 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: d14611d5b95cc32ca57dcac713b0025293cb3cd43910bc45139259865f7435f9; retrieved 2026-09-18T17:22:31.458Z.