The U.S. aircraft register, updated daily
Accidents · NTSB ENG12RA023 · Preliminary: the investigation is not finished

Boeing 777 incident near Toronto, Ca, May 28, 2012

On May 28, 2012 at about 4:29 pm local time, a Boeing 777, registered CFITW, was involved in an incident near Toronto (Toronto International Airport). It was flown under non-U.S. commercial rules. The NTSB record does not give the injuries.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this incident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 28, 2012 · about 4:29 pm local time · cases in 2012
Place
Toronto, Canada · Toronto International Airport · cases near this airport
Type
Incident
Injuries
The NTSB record does not give the injuries.
Weather
not recorded
Aircraft
Boeing 777 300ER · all 777s on the register
Registration
CFITW · registered outside the United States
Damage
Not recorded
Flight
Flight · non-U.S. commercial rules

The NTSB's narrative preliminary · quoted from the NTSB record

On May 28, 2012, at 12:29 EDT (18:29 UTC), a Boeing 777-300ER, registration C-FITW, experienced a loss of power from the No. 2, right, engine, a GE Aviation GE90-115B, shortly after takeoff from the Toronto Lester B. Pearson International Airport (CYYZ), Toronto, Ontario, Canada. Debris from the engine struck several cars causing damage, but there were no reported injuries. The investigation is under the jurisdiction of the Government of Canada. Any further information should be obtained from: Transportation Safety Board of Canada 200 Promenade do Portage Place du Centre, 4th floor Hull, Quebec, K1A 1K8 Canada website: http://www.tsb.gc.ca This report is for informational purposes only and contains only information released by or obtained from the TSB.

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

The aircraft

  • Landing gear: retractable
  • Engine: (turbofan); 0 hours total

The flight

  • Departed from: CYYZ Toronto
  • Destination: RJAA Tokyo
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Other NTSB records under CFITW the same tail number, which may have belonged to a different aircraft at the time

2018-12-11DCA19WA043 · accident near Hong Kong · substantial damage

Connections how this case links to the rest of the register

Aircraft
  • Boeing 777 359 registered today · the model family and its accident history
  • Boeing 6,678 aircraft on the register
  • Engine: · as the NTSB recorded it
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/ENG12RA023.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.