China Airlines Flight 011
Airbus Industrie A-340-300 · Incident during takeoff
From Ted Stevens Anchorage International Airport (PANC) to Taiwan Taoyuan International Airport (RCTP)
Event
- NTSB case
- ANC02IA011
- 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
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- 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
- Visual Meteorological Cond
Airbus Industrie A-340-300
- Aircraft type
- Airbus A-340
- 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
- B-18805
- Operator
- China Airlines
- Onboard fatalities
- Unknown
- Route
- From Ted Stevens Anchorage International Airport (PANC), Anchorage, AKTo Taiwan Taoyuan International Airport (RCTP), Taipei
- 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
- Part 129: Foreign
- 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
- Takeoff
- First occurrenceThe 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
- Miscellaneous/other
- 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
- Flightcrew › Crew/group coordination, inadequate
- Pilot in command › Wrong runway, selected
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During clear dark night visual meteorological conditions, the crew of an Airbus A-340-300 airplane was given a clearance to taxi to runway 32 via taxiway Romeo, and Kilo. The captain, the non-flying pilot, taxied the airplane. A relief captain occupied the center cockpit seat, and the first officer occupied the right seat. The airplane proceeded southbound on taxiway Romeo, a heading of 140 degrees, and was cleared for takeoff on runway 32 by a tower controller as the airplane was approaching taxiway Kilo. The airplane made a right turn from taxiway Romeo onto taxiway Kilo, a heading of 240 degrees, and came to a stop at the lighted hold line east of the runway 32 extension. The airplane was expected to have continued west on Kilo into the extended portion of runway 32, and then turned right (north) onto the approach end of runway 32, but the captain requested the "before takeoff checklist," and the first officer, the flying pilot, complied. Following his completion of the checklist, the captain stated, "You have control." The airplane accelerated west on taxiway Kilo. Tower controllers noticed the departure roll, and the airport's emergency phone to the fire department was activated. The local controller did not make a radio call to the crew to abort the takeoff as he felt it was too late. The airplane took off, proceeded to its destination and landed without further incident. After departure, main landing gear tire impressions were found in a snow berm at the west end of taxiway Kilo. The available taxiway distance from Romeo to the end of Kilo is about 6,800 feet. The calculated takeoff distance for the airplane was 7,746 feet. The cockpit navigation display for the Airbus A340 depicts the airplane's heading along a rotating arc near the top of the navigational display, along with a yellow airplane symbol and a white runway symbol. Taxiway Romeo and Kilo are equipped with green centerline lights having variable illumination intensity through three settings. The taxiway centerline lights for Romeo and Kilo were set on the standard (level 1) intensity level. The intersection of taxiway Kilo and Romeo has a yellow centerline stripe in the radius of the turn from Romeo to Kilo, but no centerline lights along the radius of the turn. The intersection of Kilo and the extended portion of runway 32 have a yellow centerline stripe in the radius of the turn from Kilo onto the extended centerline of runway 32, but no centerline lights along the radius of the turn. The centerline lights of Kilo did not extend through the extended portion of runway 32. Some reflective material of each taxiway centerline marking was indistinct, missing, or obscured by small patches of ice. The incident flight was the captain's first trip from Anchorage. It was the first time he flew with the first officer, and he had flown with the reserve captain on numerous occasions. The operator's aircraft operating manual for the Airbus fleet did not contain a checklist requirement for the crew to verbalize and verify the runway in use before takeoff.
Probable cause
The captain's selection of a taxiway instead of a runway for takeoff and the flightcrew's inadequate coordination of the departure, which resulted in a departure from a taxiway. A factor in the incident was inadequate airline operator's procedures that did not require the crew to verbilize and verify the runway in use prior to takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC02IA011
- Event ID
- 20020204X00182
- Case number
- ANC02IA011
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: investigation status, coordinates, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 1d061ad02b17631d6e47583ca6c83144a98b860b73b4e42614944e323dd09e88; retrieved 2026-09-18T16:06:14.532Z.