EgyptAir Flight 667
Boeing 777-266ER · Cockpit fire on ground
From Cairo International Airport (CAI) to King Abdulaziz International Airport (JED)
Event
- NTSB case
- DCA11WA090
- 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
- Unknown · led by another country; figures from NTSB notifications
- Event fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 317
- Survivors
- 317
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 7 · 2 on the ground
- 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
- Not recorded
Boeing 777-266ER
- Flight
- MS667
- Aircraft type
- Boeing 777
- 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
- SU-GBP
- Operator
- EgyptAir
- Onboard fatalities
- 0
- Route
- From Cairo International Airport (CAI)To King Abdulaziz International Airport (JED)
- Aircraft age
- Not recorded
- 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
- Non-U.S., Commercial
- 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
- Pushback/towing
- 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
- Fire/smoke (non-impact)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Not determined › Not determined
From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
On 29 July 2011, a Boeing 777 on a scheduled passenger flight from Cairo, Egypt, to Jeddah, Saudi Arabia, flying as Egyptair Flight 667, suffered a cockpit fire on the ground at Cairo Airport, while preparing to depart. There were no fatalities, but seven people were treated for smoke inhalation. The aircraft was damaged beyond economic repair.
The subsequent investigation found that the fire had originated in the crew's emergency oxygen system storage area, but was unable to conclusively determine the source of ignition, nor the cause of the oxygen leak that fuelled the fire.
Accident
The EgyptAir Boeing 777 was parked at gate F7 of Terminal 3 at Cairo airport on 29 July 2011, with preparations underway to operate flight 667. As the last few of the 307 passengers were boarding, the flight crew in the cockpit heard a bang and a hissing sound coming from the right side console, immediately followed by smoke and flames. The first officer jumped out of his seat and was ordered by the captain to leave the cockpit, while the captain unsuccessfully attempted to put out the fire using the on-board fire extinguisher.
According to the cockpit voice recorder, noises occur at 9:11:38 that the final report characterizes as "a pop is heard, followed by a hissing sound similar to the escape of pressurized gas". Three seconds later, the captain instructs the first officer to "get up, get out now." Twenty-one seconds later, the captain says "fire, fire, call for fire". The fire erupted about 30 minutes after the first officer performed a test of the oxygen mask's function during the standard pre-flight checklist. The passengers were immediately evacuated through the two connected jet bridges.
Airport fire crews arrived on the scene about three minutes after the alarm was raised and quickly extinguished the fire. Two firefighters and five passengers and crew were hospitalized for smoke inhalation.
The aircraft was subsequently written off, having sustained severe structural damage in the cockpit area as well as extensive heat and smoke damage in the cabin. This was the second hull loss of a Boeing 777 after British Airways Flight 38.
Investigation and cause
Investigation
Since the area where the fire originated has no fuel lines, oil lines, or hydraulic lines, the investigation focused on the crew oxygen supply system as the root cause or a major contributing factor. In the days after the fire, the area of the cockpit where the fire originated on SU-GBP was examined on all EgyptAir 777-200 and 777-300 aircraft. According to the investigation's final report, the wiring found in the oxygen light plate did not match the original Boeing design:
The reason for the missing clamps could not be determined. Approximately 380 early 777 aircraft did not have sleeves on the wire in the oxygen light. Boeing issued a service bulletin in October 2011 recommending that the oxygen light plate wiring be inspected and, if necessary, have sleeving installed and damaged wires replaced.
Previous testing by the US National Transportation Safety Board following a 2008 cockpit fire on a Boeing 767 had found that flexible oxygen supply hoses could ignite if anti-kink springs along the oxygen supply hose were exposed to an electric current. The hoses in SU-GBP were composed of two layers of silicone with the spring embedded in the outer layer, unlike the hose in the NTSB tests. Testing performed by Boeing on 777 crew oxygen hoses found two of the seven tested to be conductive. Further testing in conditions that increased the likelihood of ignition showed that 5 volts of direct current was not sufficient to destroy the hose. However, the final report notes that these tests were conducted on new hoses and that Boeing planned to conduct similar tests on older hoses from in-service aircraft to see if any age-related changes could have affected the results.
The same test was also performed at voltages and amperage of aircraft wiring found elsewhere in the cockpit. With air in the hose, applying 28 volts DC power at 5 amps of current or 115 volts AC power at 2.5 amps did not rupture the hose or cause ignition, but 28 V DC at 6 amps or 115 V AC at 5 amps resulted in a small leak with "some incandescence". With oxygen in the tube, 5 V DC at 1.2 amps or 28 V DC at 2.5 amps did not result in a rupture, but 28 V DC at 5 amps caused a leak "followed by ignition and complete rupture of hose." Boeing examined the design of the oxygen supply to determine possible sources of electricity:
Adiabatic heating from the sudden release of pressurized oxygen into the hose was another possible source of ignition, but ruled out. Window grease in an oxygen-rich environment was another source of ignition that was investigated, but testing determined that the oxygen level did not impact the flashpoint, which was over 200 °F above the maximum theoretical temperature in that part of the cockpit.
The investigation did not conclusively determine the cause of the fire, only that the fire originated near the first officer's oxygen mask supply tubing and that oxygen from the first officer's supply mask "is suspected to have contributed to the fire's intensity and speed", although it is not known whether a breach of the oxygen system provided a flammable environment for the fire to start or whether the oxygen system breached as a result of the fire, and an electrical fault, possibly in anti-kink springs in flexible oxygen supply hoses, may have caused the fire.
Text from the Wikipedia article “EgyptAir Flight 667” (revision 1363484076, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
Sources
Wikipedia article: EgyptAir Flight 667
- Article
- EgyptAir Flight 667
- Revision
- 1363484076 · 2026-07-10 · retrieved 2026-09-18
- Wikidata
- Q20937958
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA11WA090
- Event ID
- 20110729X51123
- Case number
- DCA11WA090
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "EgyptAir Flight 667" (page 47444633, revision 1363484076); merged with NTSB case DCA11WA090 (events / aircraft)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia: Wikipedia article coordinates
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA11WA090
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia: Wikipedia infobox: aircraft fatalities
- Ground fatalities
- Wikipedia: not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (2)
- One occurrence in two sources, merged: the Wikipedia article "EgyptAir Flight 667" and NTSB case DCA11WA090, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
- No bulk values were replaced by the NTSB case API.