Qantas Airways Flight QF768
Boeing 767 338 · Incident
From APPH · Perth to AMML · Melbourne
Event
- NTSB case
- ENG11WA003
- 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
- Incident
- 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
- Unknown
- Ground fatalities
- Unknown
- 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 767 338
- Aircraft type
- Boeing 767
- 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
- VH-OGO
- Operator
- Qantas Airways
- Onboard fatalities
- Unknown
- Route
- From APPH · PerthTo AMML · Melbourne
- 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
- Not recorded
- 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
- Not recorded
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On 12 November 2010, a Qantas Airways Boeing 767-338 airplane, registered VH-OGO, departed from Perth, Western Australia as flight QF768, a scheduled passenger service to Melbourne, New South Wales. Shortly after departure, the crew felt an engine vibration and heard popping. The engines are General Electric CF6-80C2. The captain elected to pull the #1 engine back to idle and subsequently requested a return back to Perth where the airplane landed without further incident.
The investigation is under the jurisdiction of the government of Australia. Further information pertaining to this accident may be obtained from:
Australian Transport Safety Bureau (ATSB) P.O. Box 967, Civic Square Canberra A.C.T. 2608 Australia Tel.: (61) 2 6274-6464 (61) 2 6257-4150 E-mail: atsbinfo@atsb.gov.au Fax: (61) 2 6274-6474 AFTN: ASCOYLYX Website: http://www.atsb.gov.au
The ATSB case number for this event is 201007904. This report is for informational purposes only and contains only information obtained for, or released by, the Government of Australia.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ENG11WA003
- Event ID
- 20101115X63952
- Case number
- ENG11WA003
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: coordinates, damage. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 1f59a62db1211d77d83e3c3eb63d4b6e2a9523090ac34eed1a535a4f3827a9cd; retrieved 2026-09-15T15:33:50.627Z.