FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

EVA Air Boeing 777-300 accident

16 Aug 2008 · San Francisco, CA, United States

Boeing 777-300 · Accident: ground handling event while standing

From San Francisco International Airport (SFO) to Taiwan Taoyuan International Airport (TPE)

Report a problem

Event

NTSB case
SEA08LA182
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
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

Boeing 777-300

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
B-16710
Operator
Eva Air
Onboard fatalities
Unknown
Route
From San Francisco International Airport (SFO), San Francisco, CATo Taiwan Taoyuan International Airport (TPE), 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
Standing · engine(s) operating
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
Ground handling event
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

  • Aircraft › Aircraft handling/service
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The transport airplane had been pushed back from the gate and the engines were started. Ground personnel attempted to disconnect the tow bar but had difficulty. They instructed the flight crew to release the parking brake in order to reposition the nose gear. The mechanic attempted to disconnect the tow bar and when it finally disconnected, the airplane moved forward and he was pinned under the left nose gear. The ground crew management and airline personnel indicated that the ground crew personnel were not acting in accordance with established standard operating procedures which requires that the parking brake be set prior to removal of the tow bar.

Probable cause

The ground crewman's failure to follow the tow bar disconnect standard operating procedures.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08LA182
Event ID
20080822X01296
Case number
SEA08LA182
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: 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: 583463b44c5125c640855fd21ee2ac547f9b1ce462f9bce02bf1c8928bf015d4; retrieved 2026-09-15T10:05:41.059Z.