LEVEL 3 Final report

Based on the investigation authority's final report.

Date
Show source
Occurrence
Loss of control in flight
Location
Atlantic Ocean, about 60 miles south of Nantucket, Massachusetts
Show source
Operator
EgyptAir
Show source
Aircraft
Boeing 767-366ER
Show source
Registration
SU-GAP
Show source
Route
New York JFK to Cairo, following a stop on the flight from Los Angeles
Show source
People aboard
217: 203 passengers and 14 crew members
Show source
Fatalities
217
Show source
Survivors
0
Show source
Topics
Loss of control in flight, Opposing flight control inputs, Elevator control system, Investigation disagreement

This photograph is cropped for the banner. See the full photograph, credit, licence and what it shows.

Photographs and geographic context

EgyptAir Boeing 767-366ER SU-GAP parked at Zurich Airport before the accident

SU-GAP at Zurich Airport on 20 October 1999.

Photo: Aero Icarus, CC BY-SA 2.0

Image info

The aircraft involved in flight 990, photographed eleven days before the accident.

Image source

Original photograph used without cropping or color changes. Responsive WebP copies resized without cropping.

Geographic context

Geographical orientation for EgyptAir 990New York JFK departure; Accident area south of Nantucket; Cairo destination. The flight departed New York for Cairo after arriving from Los Angeles. The accident marker uses the report's rounded center of the two wreckage fields. Airport markers are approximate geographic references.123NORTH UP / SCHEMATIC / NOT A RECORDED FLIGHT TRACK
  1. New York JFK departure
  2. Accident area south of Nantucket
  3. Cairo destination
The flight departed New York for Cairo after arriving from Los Angeles. The accident marker uses the report's rounded center of the two wreckage fields. Airport markers are approximate geographic references. Basemap: Natural Earth, public domain.
Read supporting evidence

What happened

EgyptAir flight 990 left New York for Cairo with 217 occupants. While the relief first officer was alone in the cockpit, the autopilot disconnected, the throttles moved to idle and the elevators commanded a steep descent. Nose-up movements began after the captain returned. The elevators then split, both engines were shut down and the recorders stopped. Radar showed a climb followed by a second descent into the Atlantic.

Read the full incident Follow what happened, from the flight to the investigation findings.

What investigators concluded

The NTSB attributed the accident to the relief first officer's flight control inputs. ECAA challenged that conclusion and argued that unresolved elevator component damage warranted further mechanical investigation.

Evidence behind this explanation
EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search

EgyptAir 990: departure, loss of control and investigation

1,545 words / about 8 minutes to read. Based on the investigation records cited below.

The overnight departure from New York

EgyptAir flight 990 began at Los Angeles on 30 October 1999 and stopped at New York's John F. Kennedy International Airport before its scheduled onward flight to Cairo. The Boeing 767-366ER, registered SU-GAP, had been delivered to EgyptAir in September 1989. By the accident flight it had accumulated 33,354 operating hours and 7,594 flight cycles. It carried 203 passengers, four flight crew members and ten flight attendants on the New York to Cairo leg.

The planned ten-hour flight required a command crew and a relief crew, each comprising a captain and first officer. The command crew handled departure. At about 01:20 eastern standard time on 31 October, the aircraft lifted off runway 22R. Controllers issued successive climb clearances, and at 01:35:52 New York Center cleared flight 990 to flight level 330 and directly to DOVEY intersection. The flight operated on an instrument flight rules plan in visual meteorological conditions. The captain and relief first officer had completed the required checks and training, and the NTSB found their duty and rest periods within the applicable limits.

Sources for this section

An early change at the right seat

About twenty minutes after takeoff, the relief first officer suggested taking over from the command first officer. EgyptAir crews generally arranged their own changeovers, with the command crew commonly flying the first three or four hours. The proposed change came much earlier. The command first officer initially resisted, then agreed. Sounds of seat movement, a seat belt and conversation indicated that the relief first officer occupied the right seat at about 01:42.

The aircraft leveled at 33,000 feet at 01:44:27. At 01:47:39 the captain reported on a new radio frequency, the aircraft's last transmission to air traffic control. Shortly afterward, the relief first officer asked someone to return a pen to another first officer in the cabin. At 01:48:03 the captain said he was going to the toilet. The voice recorder captured his seat motor and then a sound resembling the cockpit door. The NTSB's examination of the recorded voices and sounds placed the relief first officer alone in the cockpit from about 01:48:19 until the captain returned.

Sources for this section

The first descent

The autopilot disconnected at 01:49:45. The aircraft remained essentially level for about eight seconds, with only small elevator movements and a slow left roll. No disconnect warning sounded. The NTSB judged this consistent with a manual disconnect. At 01:49:53 the throttles moved from cruise power to idle, followed one second later by a sustained nose-down elevator movement. The throttle levers traveled faster and farther aft than the automatic throttle system could command. The NTSB attributed their movement to the relief first officer.

As the aircraft pitched down, its load factor fell toward zero. Further nose-down elevator movement at about 01:50:05 produced briefly negative loads. At 01:50:06 the captain returned, asking what was happening. The relief first officer continued repeating a quiet Arabic phrase translated by the recorder group as 'I rely on God.' EgyptAir and ECAA explained that Egyptians commonly used the phrase to ask God's assistance in everyday activities. The captain's questions received no explanation of the developing emergency.

At 01:50:08 the aircraft exceeded its maximum operating speed of Mach 0.86, and a warning sounded. The pitch reached about 40 degrees nose down at 01:50:15, with the wings remaining close to level. The calculated descent rate reached approximately 39,000 feet per minute at 01:50:19. Four seconds later the calculated airspeed peaked at Mach 0.99.

Sources for this section

Recovery inputs, split elevators and engine shutdown

At 01:50:15, while the aircraft was passing about 27,300 feet, both elevators began moving toward a nose-up command. The descent rate started to decrease. The NTSB considered these movements likely to have resulted from the captain's inputs after his return. At 01:50:21 the elevators passed through neutral into nose-up positions. The right elevator then reversed toward nose down, while the left continued nose up. This split persisted through the end of the flight data recording.

Between 01:50:21 and 01:50:23, both engine start levers moved from run to cutoff, stopping the fuel supply. The levers were spring-loaded switches that required lifting out of a detent before movement. Soon afterward, the throttles advanced fully and the speedbrake handle moved to its deployed position. The captain questioned the engine shutdown and repeatedly called for the relief first officer to pull with him. The NTSB attributed the shutdown to the relief first officer and the throttle and speedbrake movements to the captain.

The flight data recorder stopped at 01:50:36.64 and the cockpit voice recorder at 01:50:38.47. The NTSB found the cessation consistent with electrical power loss following the engine shutdown. At the last recorded instant the aircraft's pitch had risen to about eight degrees nose down and its load factor to about 2.4 G. The left elevator still commanded nose up and the right commanded nose down.

Sources for this section

The climb, second descent and recovery of wreckage

Primary radar returns continued after the recorders stopped. The NTSB combined those returns with aircraft performance calculations to reconstruct the remaining movement. The first descent ended at about 16,000 feet. The aircraft then climbed to about 25,000 feet by approximately 01:51:15, changing heading from about 80 degrees to about 140 degrees. A second rapid descent followed. The estimated ocean impact time was about 01:52:30. All 217 occupants were killed.

Two underwater debris fields lay about 1,200 feet apart, centered near 40 degrees 21 minutes north and 69 degrees 46 minutes west. The western field mainly contained the left engine and smaller pieces; the eastern field contained most of the fuselage, wings, tail, right engine and recorders. The NTSB concluded that the aircraft remained intact through the initial dive and climb, with separation occurring during the last descent. About seventy percent of the aircraft was recovered in the first operation, which ended on 22 December 1999. A further recovery in March and April 2000 brought up the left engine and additional wreckage.

Sources for this section

Testing the elevator failure scenarios

Each outboard elevator was driven by three hydraulic power control actuators, with each actuator supplied by a separate hydraulic system. The captain's control column connected directly to the left elevator system and the first officer's to the right. Linkages and override mechanisms normally coordinated the two sides. Testing showed that opposing control column forces could activate an override and produce elevator movements in different directions.

Investigators recovered four of the six actuators. One contained a sheared spring-guide pin and a displaced spring coil. The NTSB could not determine whether those conditions preceded impact. Several recovered bellcrank assemblies also had sheared rivets. Ground tests and calculations examined four principal combinations of jams, disconnected actuator linkages and a jammed and broken control cable. Predicted elevator positions were compared with the recorded sequence. For the three actuator scenarios, the initial predicted failed-surface deflection was approximately six degrees nose down, compared with the recorded movement of about 3.6 degrees.

The NTSB ruled out the evaluated mechanical failure scenarios because their predicted movements diverged from the flight recorder data. Simulator trials involving pilots from EgyptAir, Boeing, the FAA and NTSB produced recoveries using either control column with the modeled failures. Those simulations assumed that the other pilot was not applying opposing inputs. Testing also reproduced split elevator positions with opposing pilot forces.

The recorder measured elevator positions but did not record control column positions or forces. Investigators therefore reconstructed the pilots' inputs from the aircraft movements, system tests and cockpit sounds. The simulator also did not reproduce the negative loads experienced during the dive. The NTSB evaluated that limitation and considered the recovery tests valid.

Sources for this section

ECAA's disagreement

Egypt was the state of registry and held jurisdiction under Annex 13. At the Egyptian government's request, the NTSB assumed responsibility for the investigation, with ECAA participating through an accredited representative. ECAA's response to the NTSB draft report appears in Attachment B of the published brief. ECAA rejected the pilot-action conclusion, arguing that the investigation and analysis were incomplete and that evidence of intent or motive was absent.

ECAA emphasized the sheared and deformed elevator bellcrank rivets, including failures found on other 767 aircraft, and the unusual damage inside a recovered actuator. It argued that these abnormalities pointed to a possible elevator system defect and potential actuator jams. It also challenged the simulation and aerodynamic analysis near the speed of sound, stating that validated Boeing data extended only to Mach 0.91 while flight 990 reached approximately Mach 0.99. ECAA requested further testing and disputed the NTSB's interpretation of the elevator split as opposing pilot commands. Its response argued that high-speed aerodynamic forces required closer investigation.

Sources for this section
EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search
EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search

The NTSB finding and safety actions

The NTSB adopted its final aircraft accident brief on 13 March 2002. It determined that flight 990 departed normal cruise and struck the Atlantic Ocean as a result of the relief first officer's flight control inputs. Its findings attributed the later elevator split to opposing inputs from the two pilots. The reason for the relief first officer's actions was not determined.

During the investigation, Boeing and the FAA examined bellcrank rivet failures across the 767 fleet. FAA directive AD 00-17-05 required a one-time functional check of elevator bellcrank shear rivets, with rework or replacement when necessary. AD 01-04-09 subsequently required repetitive elevator control testing at least every 400 flight hours and further inspections as needed. ECAA's response described its June 2000 recommendations for cockpit indications of abnormal actuator operation, examination of the control system design, and procedures for uncommanded elevator movement. The NTSB also cited recommendations A-00-30 and A-00-31 for crash-protected cockpit image recording to improve investigation evidence.

Sources for this section

Return to the short summary / Source status and limitations

How the sequence developed

Follow the main stages, then open the evidence beneath each step.

  1. Manual inputs before the dive

    The NTSB attributed the autopilot disconnect and throttle movement to the relief first officer while he was alone in the cockpit.

    Read supporting evidence
  2. Sustained nose-down elevator movement

    Both elevators moved nose down and the aircraft entered a steep, accelerating descent from cruise altitude.

    Read supporting evidence
  3. Recovery followed by opposing commands

    Both elevators initially moved toward nose up after the captain returned, then split. The NTSB attributed the split to opposing inputs from the two pilots.

    Read supporting evidence
  4. Shutdown, climb and second descent

    The engine start levers moved to cutoff. After the recorders lost power, primary radar showed a climb and then a second rapid descent to the ocean.

    Read supporting evidence

A simplified reading of the investigation findings. The sequence does not replace the full report or imply that every contributing factor is shown.

Sequence of events

Times are eastern standard time, using the flight recorder and air traffic control chronology in the NTSB brief. Earlier arrival and crew transport times in the report use eastern daylight time. Expand an event to see its evidence.

  1. 01:20Departure from JFK
  2. About 01:42Relief first officer takes the right seat

    The relief first officer replaced the command first officer earlier than the usual changeover.

  3. 01:44:27Cruise at 33,000 feet

    The aircraft leveled at its assigned flight level 330.

  4. About 01:48:19Captain leaves the cockpit

    The NTSB determined that the relief first officer remained alone until the captain returned during the dive.

  5. 01:49:45 to 01:49:54Autopilot disconnect, idle thrust and pitchover

    The autopilot disconnected. Eight seconds later the throttles moved to idle, followed by abrupt nose-down elevator movement.

  6. 01:50:06 to 01:50:15Captain returns and recovery movement begins

    The captain returned asking what was happening. Both elevators began moving toward nose-up commands as the aircraft passed about 27,300 feet.

  7. 01:50:21 to 01:50:23Elevators split and engines shut down

    The left elevator commanded nose up and the right nose down. Both engine start levers moved to cutoff.

  8. 01:50:36.64 to 01:50:38.47Recordings end

    The flight data and cockpit voice recordings ended after engine shutdown and associated electrical power loss.

  9. About 01:51:15Climb ends and second descent begins

    Primary radar indicated a climb to about 25,000 feet before the aircraft began its final descent.

  10. About 01:52:30Impact in the Atlantic

    The performance study estimated ocean impact at about 01:52:30. All 217 occupants were killed.

Search the report evidence

Search extracted report prose, with original page references. Short results link to the full document.

Questions readers ask

Why did the NTSB attribute the throttle movement to the relief first officer?

The throttles moved to idle at more than twice the rate the automatic throttle system could command and beyond its minimum commanded position. The NTSB attributed that movement to manual inputs from the relief first officer, who was alone in the cockpit.

What elevator damage did investigators recover?

A recovered actuator had a sheared spring-guide pin and a displaced spring coil. The NTSB could not determine whether those conditions preceded impact. ECAA argued that the unusual actuator damage and bellcrank rivet failures indicated a possible elevator defect.

EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search
Why did ECAA challenge the high-speed testing?

ECAA said validated Boeing data extended only to Mach 0.91 and challenged extrapolation to the higher speeds reached by flight 990. Its response requested further wind tunnel testing and disputed the explanation of the elevator split.

What the evidence can and cannot establish

ECAA disagreement

ECAA rejected the NTSB pilot-action conclusion, emphasized possible elevator defects and challenged the high-speed performance testing.

Read supporting evidence
EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search
EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search

Control forces and simulation conditions

The flight data recorder captured elevator positions but did not record control column positions or forces. NTSB simulations reproduced opposing inputs, but did not reproduce the negative loads experienced during the dive.

Read supporting evidence

Unresolved actuator damage

Investigators found a sheared pin and displaced spring coil in a recovered actuator. The timing of that damage relative to impact could not be determined.

Read supporting evidence

Safety follow-up

Actions and recommendations are described at the dates of the cited records. A recommendation is not proof of implementation.

767 elevator inspection requirements

AD 00-17-05 required a one-time check of elevator bellcrank shear rivets in 2000. AD 01-04-09 required repetitive elevator control testing at least every 400 flight hours from 2001.

Read supporting evidence

ECAA safety recommendations

ECAA described three recommendations sent to the FAA on 4 June 2000: indications of abnormal actuator operation, further examination of elevator control design and bellcrank discrepancies, and crew procedures for uncommanded elevator movement.

Read supporting evidence

Cockpit image recording recommendations

The NTSB cited recommendations A-00-30 and A-00-31 for crash-protected cockpit image recording systems. At the brief's adoption, their status was Open, Unacceptable Response.

Read supporting evidence

Classifications, with reasons

These labels organise the evidence. They are not a ranking of causes. A shared label means a shared research topic, not an identical mechanism.

Accident sequenceLoss of control in flight

A sustained nose-down elevator movement initiated a rapid descent from 33,000 feet, followed by a climb and a second descent into the ocean.

NTSB findingOpposing flight control inputs

The NTSB attributed the elevator split to the captain commanding nose-up movement and the relief first officer commanding nose-down movement.

Investigation evidenceElevator control system

The NTSB evaluated actuator jams and disconnected control linkages. ECAA disputed the mechanical failure analysis and emphasized damaged actuators and bellcrank rivets.

EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search
ECAA positionInvestigation disagreement

ECAA challenged the NTSB pilot-action conclusion and the completeness of the mechanical and high-speed performance investigation.

EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search

Read alongside

These comparisons connect specific research topics. Shared circumstances do not establish identical causes. Evidence from both investigations is provided below.

Alaska Airlines Flight 261

EgyptAir 990 and Alaska Airlines 261 both involved loss of pitch control and ocean impact. Alaska 261's NTSB report identified failure of the stabilizer jackscrew nut threads from excessive wear and insufficient lubrication. For EgyptAir 990, the NTSB attributed the accident to flight control inputs, while ECAA disputed the exclusion of elevator defects.

Read supporting evidence
EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999Attachment B, ECAA disagreement, opening statement | Printed page Attachment B, opening page | PDF page 118Find this passage in evidence search
NTSB final reportExecutive summary, probable cause | Printed page xii | PDF page 14Find this passage in evidence search

Further investigation records

Explore the records below for additional context. They open on the publisher's site and are not all included in our report search. Source reuse terms apply.

  • NTSB/AAB-02/01

    NTSB / investigation record

    The final aircraft accident brief includes the factual investigation, analysis, probable cause, voice recorder transcript and ECAA response.

Sources and transparency

NTSB final aircraft accident brief adopted 13 March 2002, including ECAA's response to the draft findings.

Source limitations

The final descent was reconstructed from seven primary radar returns. Their altitude estimates were subject to potentially large errors.

EgyptAir Flight 990, Boeing 767-366ER, SU-GAP, 60 Miles South of Nantucket, Massachusetts, October 31, 1999

National Transportation Safety Board
Final aircraft accident brief NTSB/AAB-02/01, adopted 13 March 2002; corrected edition dated 27 March 2002

Official report PDF, hosted by ntsb.gov

Open source document

160 PDF pages.

Original factual commentary with short supporting quotations. The complete official publication is available from the NTSB. Source terms.

Read the extraction, classification and review methodology.

Suggest a correction to this dossier

Editorial record

Kevin Murphy writes the incident accounts on AirlineIncidents.com, out of a long interest in aviation safety and the lessons each investigation leaves behind.

Prepared by
AirlineIncidents editorial desk
Report citation check
Independent expert review
Not completed

Citation checks compare supporting text with the indexed report pages. They do not constitute independent expert review. How these pages are prepared.

Revision history

: NTSB final aircraft accident brief adopted 13 March 2002; ECAA response included as Attachment B.

Source-based corrections are reviewed before changes appear here. Suggest a correction to this dossier.

Cite or link to this page

Quoting this account or linking to it? Please use the page address below, and credit the investigation report it is built from.

Credit line

AirlineIncidents.com. EgyptAir Flight 990 accident account. Published 15 October 2026. https://airlineincidents.com/incidents/egyptair-990-1999/

HTML link

<a href="https://airlineincidents.com/incidents/egyptair-990-1999/">EgyptAir Flight 990 accident account (AirlineIncidents.com)</a>

Select a box to copy it. Spotted something wrong? Send a correction.