Aviation Crash Map

Boeing 737 N27266

8 June 2025 · Phoenix, Arizona, United States · Serious injuries

Summary

On 8 June 2025 at about 14:00 local time, a Boeing 737 registered N27266, operated by United Airlines, was involved in an accident near Phoenix, Arizona, United States. 167 people were on board and one was seriously injured, 3 had minor injuries. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 14:00
Classification
Accident
Location
Phoenix, Arizona, United States
Nearest airport
Phoenix Sky Harbor Internation (PHX)
Coordinates
33.4343, -112.0120
Aircraft
Boeing 737
Registration
N27266
Category
Airplane
Year built
2021
Engines
2
Operator
United Airlines
Operating rule
Part 121: Air Carrier
Phase of flight
Not recorded
Route
Unknown → Newark
Aircraft damage
Not recorded
Weather
VMC
Light
Day
NTSB number
DCA25LA230

People

1 person was seriously injured.

On board Died Serious Minor Uninjured
167 0 1 3 163

Probable cause

The abrupt application of brakes during taxi, which resulted in a sudden stop and caused a flight attendant to sustain a serious injury.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

United Airlines flight 716, came to a sudden stop while taxiing out of the gate area and trying to make a turn onto taxiway C at Phoenix Sky Harbor International Airport (PHX), Phoenix, Arizona. As a result of the abrupt stop, one flight attendant (FA) sustained a serious injury. The event flight returned to the gate and emergency medical services were called. Flight 716 was a scheduled passenger flight from PHX to Newark Liberty International Airport (EWR), Newark, New Jersey, with a planned departure time of 0700 MST. The flight crew reported that this was the first flight of the day. The captain was the pilot flying, and the first officer (FO) was the pilot monitoring. According to the flight crew, there were no operational pressures, and following a normal pushback and engine start-up, the airplane was positioned on Taxiway Z facing north, holding short of Taxiway C, where they contacted Airport Traffic Control Tower (ATCT) ground control for taxi clearance (see figure 1). Ground control issued the standard southbound taxi route, which they had reviewed during the pilot briefing. The captain confirmed the instructions with the FO that they would turn right on Taxiway C, then right on Taxiway S, holding short of Taxiway D. According to the flight crew, while taxiing at a speed below 10 knots, the FO noticed they were beginning to pass Taxiway C. The FO alerted the captain that they needed to turn right to enter Taxiway C. The captain applied the brakes to assist with the turning maneuver, using what he recalled felt like normal pressure. Initially, everything seemed normal, but shortly afterward, the flight crew indicated that they felt that the brakes responded more aggressively than expected, causing the airplane to come to an abrupt stop. Both crew members confirmed there was sufficient space to complete the turn safely. Figure 1. Image of the taxi route for flight 716. (Source: United Airlines) According to the forward FA’s, after the airplane had departed from the gate and was taxiing out to the runway, they had started showing the safety demonstration video. Shortly after that, the airplane came to an abrupt stop. Both FAs were in the forward galley at the time and were thrown into the metal counter and safety latches. Each reported experiencing sharp pain in the neck, back, and legs as a result of the sudden jolt. As the airplane entered Taxiway C, the flight crew received a call from one of the forward FA’s indicating that the other forward FA was injured and she needed to go back to the gate. The flight crew coordinated with PHX operations, ramp, and ground control to return to the gate. Paramedics met the airplane at the gate and transported the injured FA to the hospital where they were diagnosed with a serious injury. According to United Airlines, their maintenance personnel conducted a post-accident general visual inspection of the airplane’s brake system and reported no anomalies were found. The airplane was subsequently placed on jacks, and the wheels were manually rotated. No evidence of brake dragging or grabbing was observed during this procedure. The brake system was cycled multiple times while the wheels were spun, and no faults or irregularities were identified. A review of maintenance history for this airplane showed that there were two maintenance entries for the braking system in the previous 90 days. Both entries were due to broken clips and were not related to braking actions.

Quoted verbatim from the NTSB record.

Other Boeing 737 accidents

Date Aircraft Location Operator Outcome Died
4 Apr 2025 Boeing 737
SP-ESL
Muharraq Island, Bahrain Enter Air Sp. z o.o No injuries -
17 May 2025 Boeing 737
G-NPTA
Edinburgh, United Kingdom
no coordinates
West Atlantic Unknown -
13 Mar 2025 Boeing 737-823
N885NN
Denver, Colorado, United States American Airlines Minor injuries -
2 Jul 2025 Boeing 737
VH-YFZ
Melbourne Airport, Australia
no coordinates
Virgin Australia Airlines PTY LT Unknown -
15 May 2025 Boeing 737
SP-ESG
Kos, Greece Enter Air Sp. Z o.o No injuries -
22 Apr 2025 Boeing 737
G-CRUX
Luton, United Kingdom
no coordinates
- Unknown -

All 1,317 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
7 Jul 2025 Piper PA-22-160
N9019D
Page, Arizona, United States - No injuries -
1 Oct 2025 Amazon Com Services MK30
N791PA
Tolleson, Arizona, United States Amazon.com Services LLC No injuries -
1 Oct 2025 Amazon Com Services MK30
N579PA
Tolleson, Arizona, United States Amazon.com Services LLC No injuries -
11 Jul 2025 Pipistrel ALPHA TRAINER
N209ZM
Colorado City, Arizona, United States - No injuries -
26 Sep 2025 Cessna 150F
N8171S
Lake Havasu City, Arizona, United States - Minor injuries -
29 May 2025 Cessna T210M
N6419B
Tucson Estates, Arizona, United States - No injuries -

All 170,864 records in United States