Boeing 777 incident near Mt. Wilson, California, December 16, 2016
On December 16, 2016 at about 9:25 am local time, a Boeing 777, registered B16726, was involved in an incident during enroute (climb to cruise) near Mt. Wilson, California (Los Angeles International Airp airport). It was flown under foreign airline rules (Part 129). The NTSB record does not give the injuries. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The incident was caused by the air traffic controller assigning the pilots a left turn instead of the required right turn after departure which placed the aircraft in an unsafe proximity with terrain and obstructions. Contributing to the incident was the air traffic controller's inadequate recovery technique during the development of the incident.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 16, 2016 · about 9:25 am local time
- Place
- Mt. Wilson, California · Los Angeles International Airp · map
- Type
- Incident
- Injuries
- The NTSB record does not give the injuries.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Boeing 777 35EER · all 777s on the register
- Registration
- B16726 · no longer on the register · serial 44552
- Damage
- Not recorded
- Flight
- Flight · foreign airline rules (Part 129)
The NTSB's narrative final · quoted from the NTSB record
A near controlled flight into terrain (CFIT) incident occurred near Mt. Wilson, California, when a Boeing 777-300 departing Los Angeles International Airport (LAX) was instructed to turn left toward rising terrain after departure from runway 07R. The aircraft was operating on a 14 Code of Federal Regulations Part 129 international flight. Air traffic control services were provided by the Federal Aviation Administration Southern California Terminal Radar Approach Control (SCT TRACON). There was no damage reported to the aircraft, and no reported injuries to the passengers or crew. Due to weather in the area, LAX was operating in an east flow configuration with aircraft departing to the east. The Boeing 777-300 pilot contacted the SCT controller and was given an initial climb to 7,000 feet. A short time later, the SCT controller instructed the pilot to turn left to a heading of 180 degrees which required a left 270 degree turn. The turn resulted in the aircraft turning toward rising terrain and back toward the airport; normal procedures in an east flow would have been for a right turn to a heading of 180 degrees. While in the left turn, the pilot requested a high speed climb which resulted in the aircraft accelerating beyond the 250 knot LAX class B speed restriction and required additional airspace in order to complete an assigned turn. After recognizing the aircraft was in a left turn, the SCT controller issued the crew a right turn to a heading of 180 degrees. As the aircraft began to turn right, the air traffic controller instructed the crew to expedite the turn due to recognizing a developing proximity issue with another aircraft that had departed from LAX. The air traffic controller stopped the climb of the B777-300 and issued a left turn to a heading of 270 degrees. These turns in quick succession, combined with the speed of the aircraft, resulted in the flight tracking northbound toward rising terrain. The closest lateral and vertical proximity between the airplane and terrain/obstructions was about 0.3 miles and 0 ft, respectively, which is less than the minimum separation requirements.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Air traffic event during initial climb
- Air traffic event during enroute (climb to cruise) defining event
- Terrain avoidance alert during enroute (climb to cruise)
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action selection › ATC personnel
- factor Personnel issues › Task performance › Communication (personnel) › Interpretation/understanding › ATC personnel
- Personnel issues › Experience/knowledge › Training › Total instruct/training recvd › ATC personnel
- Personnel issues › Action/decision › Action › Lack of action › ATC personnel
- Personnel issues › Experience/knowledge › Experience/qualifications › (general) › ATC personnel
The aircraft
- Landing gear: retractable
- Engine 1: (type not recorded); 0 hours total
- Engine 2: (type not recorded); 0 hours total
- Operator: Eva Air
The flight
- Departed from: LAX Mt. Wilson CA at 9:25 am
- Destination: RCTP Taiwan Taoyuan
- Flight plan: IFR
- Runway 07R, 11,095 ft by 200 ft
- A second pilot was aboard
Weather at the time
- Light: night, dark
- Wind: from 090° at 8 knots, gusting 15
- Visibility: 1.2 statute miles
- Sky: overcast at 400 ft
- Temperature: 55°F (13°C), dew point 55°F (13°C)
- Altimeter: 29.87 inHg
- Observation at 9:44 am from LAX, 24 miles away
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on May 6, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Air Traffic Control Factual Report | PDF, 17 pages | View Download |
| 2 | Air Traffic Control Attachment 1 - Interview Summaries | PDF, 29 pages | View Download |
| 3 | Air Traffic Control Attachment 2 - Mandatory Occurrence Report | PDF, 5 pages | View Download |
| 4 | Air Traffic Control Attachment 3 - EVA015 Crew Statements | PDF, 9 pages | View Download |
| 5 | Air Traffic Control Attachment 4 - Enhance Ground Proximity Warning System Data (EGPWS) | PDF, 11 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
