FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

USA Jet Airlines Flight JUS834

24 Mar 2023 · Saltillo, Mexico

McDonnell Douglas Aircraft Co MD-88 · Accident: tailstrike during landing

From Willow Run Airport (KYIP) to an unrecorded destination

Report a problem

Event

NTSB case
DCA23LA232
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
Unknown
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

McDonnell Douglas Aircraft Co MD-88

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
N834US
Onboard fatalities
Unknown
Route
From Willow Run Airport (KYIP), Belleville, MITo not recorded
Aircraft age
About 33 years (built 1990)
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
Landing
Defining eventThe 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
Tailstrike
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

USA Jet Airlines, flight JUS834, sustained a tailstrike while landing at the Saltillo/Plan De Guadalupe International Airport (SLW), Saltillo, Mexico. After the event, the airplane completed two additional flights before the damage was discovered by maintenance personnel. The flight was an on-demand international cargo flight from Willow Run Airport (YIP), Detroit, Michigan, to SLW.

The flight crew stated that, upon arrival at SLW, they conducted an instrument landing system (ILS) approach to runway 17. A review of flight data recorder (FDR) data revealed that the autopilot and autothrottle were disconnected at about 1,400 ft above ground level (agl). The airplane was in a stabilized configuration on approach, with glideslope and localizer deviations of less than one dot. Airspeed varied by less than 5 knots and the sink rate was less than 1,000 feet per minute (fpm).

The crew indicated that the flight was “slightly bumpy” on final approach with small fluctuations in airspeed. They stated that it felt as though the wind had shifted or dissipated rapidly while approaching 50 feet agl resulting in a higher-than-normal sink rate. FDR data showed that near 80 ft radio altitude (RA), the aircraft’s sink rate began to increase rapidly, indicating a sudden decrease in headwind. The control column was deflected airplane nose-up (ANU) in an apparent attempt to arrest the sink rate.

FDR data showed that the control column remained deflected ANU until about 30 ft RA, when the airplane’s pitch increased to nearly 5 degrees ANU. Subsequently, an airplane nose-down (AND) column input was initiated. The airplane continued to descend at a sink rate of over 15 feet per second (fps) just before touchdown, resulting in a hard landing with a peak vertical acceleration of 3.24 gravitational force equivalent (g). The tail strike likely occurred at the touchdown point where the airplane's pitch attitude reached approximately 8 degrees, exceeding the attitude limit where the aft body of the aircraft would contact the ground I don’t see anything in the docket supporting this? Did this come from a manufacturer's manual we can add a page from? They have a graph or chart usually that has this info. once the landing gear was compressed. Based on this information, and a review of several takeoffs and landings led to the determination that the tailstrike occurred at SLW. The crew indicated that the aircraft touched down harder than normal, that the airplane did not bounce, and they did not feel as if a tail strike had occurred.

During a post-flight inspection at SLW, the crew stated that they did not observe any damage to the fuselage and the tail skid assembly's tailstrike indicator was in a horizontal position (parallel to the fuselage), indicating a tail strike had not occurred, see figure 1. The trip continued from SLW to Windsor Airport (YQG), Windsor, Ontario Canada, and then to YIP. During a maintenance pre-flight inspection at YIP a day after the accident, external damage to the fuselage, missed during the flight crew’s walk-around in SLW, was discovered. Further inspection of the airplane revealed substantial damage to internal structural members of the lower fuselage.

Indicator

Figure 1. Photo of skid assembly on airplane with tailstrike indicator position shown. (Source: Boeing)

The tail skid assembly was removed from the airplane and sent to the Boeing equipment quality analysis (EQA) laboratory for examination. No mechanical anomalies were found with the unit that would have affected the tail bumper strut from properly stroking and rebounding when pressurized and installed on the airplane. Although contamination, metallic and organic, larger than the design specification was found within the unit, it could not be determined how it affected the operation of the unit.

Probable cause

The pilot's failure to adequately compensate for a wind shift while on short final approach which resulted in a higher than normal sink rate and a tailstrike.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA23LA232
Event ID
20230411107036
Case number
DCA23LA232
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 626110ceb0807edf7bfafb5ea7e343375d984be799eb6d95fe11e1e711c8bca6; retrieved 2026-09-16T17:29:53.796Z.