Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

January 10, 2025 · Boeing 767 34AF · N324UP

San Bernardino, CA

Overview

Report Status
Probable Cause
Event Type
Accident
Date
January 10, 2025
Injury Outcomes
No injuries (3 uninjured)
Location
San Bernardino, CA
Aircraft
Boeing 767 34AF (1998)
Tail Number
N324UP
Operator
United Parcel Service
Injuries
None
Aircraft Damage
Substantial
NTSB Number
DCA25LA085

United Parcel Service (UPS) flight 2918 experienced a tailstrike while landing on runway 6 at San Bernardino International Airport (SBD), San Bernardino, California. The non-scheduled cargo flight was operated under the provisions of 14 Code of Federal Regulations Part 121. The airplane sustained substantial damage to the underside of the fuselage near the tail. Flight 2918 was originally destined for Ontario International Airport (ONT), Ontario California. After a missed approach at ONT, the flight crew elected to divert to SBD due to fuel state and unfavorable wind conditions at ONT. According to the flight crew, the approach into SBD was stabilized at both 1,000 and 500 ft above ground level (agl). The flight crew further stated that during landing on runway 6, the captain began a normal flare at about 100 ft agl, but he felt the airplane “nose come up and sink rate accelerate” at about 15 ft. The captain stated the airplane contacted the runway “slightly more firmly than usual” but it did not bounce. Once on the runway, the flight crew received an aural windshear warning. Flight data showed the airplane’s pitch attitude reached a maximum of 8.1° at touchdown, sufficient to cause contact between the airplane’s lower fuselage and the runway. Additionally, flight data showed a vertical acceleration of 2.2g, and a windshear warning simultaneous with the touchdown that lasted about 5 seconds. An unscheduled stabilizer trim movement warning occurred immediately after the touchdown. Lastly, an unscheduled stabilizer movement, consistent with the tailstrike event, occurred momentarily about half a second after touchdown. During postlanding rollout, the captain recalled seeing a “tail skid” message on the engine indicating and crew alerting system (EICAS). During postlanding taxi, the first officer was unable to reset the stabilizer trim. Postlanding inspection by the captain revealed substantial damage to the lower fuselage consistent with its contact with the runway. Further inspection of the airplane found damage to the tail skid shock strut and its support assembly as well as the horizontal stabilizer ballscrew actuator (jackscrew), both as a result of the tailstrike. The tail skid damage was consistent with the tail skid message observed on the EICAS by the flight crew. The flight data showed no evidence of a mechanical malfunction that would have contributed to the airplane pitch angle when the airplane touched down on the runway.

NTSB Probable Cause

Environmental issues-Conditions/weather/phenomena-Wind-Windshear-Ability to respond/compensate

Full Narrative

United Parcel Service (UPS) flight 2918 experienced a tailstrike while landing on runway 6 at San Bernardino International Airport (SBD), San Bernardino, California. The non-scheduled cargo flight was operated under the provisions of 14 Code of Federal Regulations Part 121. The airplane sustained substantial damage to the underside of the fuselage near the tail. Flight 2918 was originally destined for Ontario International Airport (ONT), Ontario California. After a missed approach at ONT, the flight crew elected to divert to SBD due to fuel state and unfavorable wind conditions at ONT. According to the flight crew, the approach into SBD was stabilized at both 1,000 and 500 ft above ground level (agl). The flight crew further stated that during landing on runway 6, the captain began a normal flare at about 100 ft agl, but he felt the airplane “nose come up and sink rate accelerate” at about 15 ft. The captain stated the airplane contacted the runway “slightly more firmly than usual” but it did not bounce. Once on the runway, the flight crew received an aural windshear warning. Flight data showed the airplane’s pitch attitude reached a maximum of 8.1° at touchdown, sufficient to cause contact between the airplane’s lower fuselage and the runway. Additionally, flight data showed a vertical acceleration of 2.2g, and a windshear warning simultaneous with the touchdown that lasted about 5 seconds. An unscheduled stabilizer trim movement warning occurred immediately after the touchdown. Lastly, an unscheduled stabilizer movement, consistent with the tailstrike event, occurred momentarily about half a second after touchdown. During postlanding rollout, the captain recalled seeing a “tail skid” message on the engine indicating and crew alerting system (EICAS). During postlanding taxi, the first officer was unable to reset the stabilizer trim. Postlanding inspection by the captain revealed substantial damage to the lower fuselage consistent with its contact with the runway. Further inspection of the airplane found damage to the tail skid shock strut and its support assembly as well as the horizontal stabilizer ballscrew actuator (jackscrew), both as a result of the tailstrike. The tail skid damage was consistent with the tail skid message observed on the EICAS by the flight crew. The flight data showed no evidence of a mechanical malfunction that would have contributed to the airplane pitch angle when the airplane touched down on the runway.

Flight

Event TypeAccident
Event Time18:55 PST
Nearest AirportSan Bernardino Intl (0nm ESE)
Runway06/2
Runway Length10000 ft
Runway Width200 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBoeing 767 34AF
Tail NumberN324UP
Aircraft CategoryAir
DamageSubstantial
OperatorUnited Parcel Service
Operating RulePart 121
Engines2
Engine TypeTurbofan
Engine DetailsGe · CF6-80 SERIES · Turbofan · 57078 | Ge · CF6-80 SERIES · Turbofan · 56218
Seats6

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 32 · First Class · None
Crew 2None
Crew 3Age 53 · First Class · None

Conditions

ConditionsVMC
LightNight
Wind360° @ 5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point66 F / 0 F
Altimeter30.15 inHg
Observation Time17:55
Weather SourceWFAC

Appendix: Source Data