FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Philippine Airlines Flight 103

6 Jun 1999 · Los Angeles, CA, United States

Boeing 747-4F6B 747-400 and Boeing 747-SP · Accident: collision between aircraft (not in flight) while taxiing

Report a problem

Event

NTSB case
LAX99FA218
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
0
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

Aircraft 1 · Boeing 747-4F6B 747-400

Aircraft type
Boeing 747
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
N751PR
Onboard fatalities
Unknown
Route
From Los Angeles International Airport (LAX), Los Angeles, CATo Ninoy Aquino International Airport (MNL), Manila
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
Taxi · to runway
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
Collision between aircraft (not in flight)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Aircraft 2 · Boeing 747-SP

Aircraft type
Boeing 747
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
F-GTOM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Grand Bahama International Airport (FPO), ParisTo Los Angeles International Airport (LAX)
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) not operating
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
Collision between aircraft (not in flight)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Airport personnel › Airport operations, improper
  • Ground personnel › Improper use of procedure
  • Ground personnel › Information unclear

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

NTSB narrative

At night, a Boeing 747-4F6B, N751PR, taxied into a Boeing 747 SP-44, F-GTOM. During the collision, N751PR was proceeding westbound on taxilane "C" for its planned departure for Manila. F-GTOM had landed from France and was standing short of its assigned gate 101. F-GTOM was oriented in a northwesterly direction, and its left wing was extending onto taxilane "C". Six ground service personnel were in proximity to F-GTOM, awaiting the connection of a tow tractor to pull it into the gate at the Tom Bradley International Terminal (TBIT). During the collision sequence, N751PR impacted the aft portion of F-GTOM's left wing. N751PR's right wing's winglet was severed off and F-GTOM's left wing was substantially damaged.

ATC had cleared the departing N751PR to taxi past the standing F-GTOM and make a 90-degree turn onto a nearby taxiway. The ground crew's wing walkers for the standing airplane were aware that its left wing was partially blocking taxilane "C." One of the wing walkers issued its company-authorized "engine operating" signal that was observed by N751PR's crew. This nonstandard signal was interpreted by the departing airplane's crew as an "all clear to taxi" signal in accordance with the standard hand signals published in the FAA's Aeronautical Information Manual and by its airline.

The collision occurred as the departing airplane commenced a sharp left turn, from the centerline of taxilane "C" toward a perpendicular taxiway. During the turn the effective length of the airplane's wing increased. The right wing tip was not visible to the captain, and he relied upon his first officer and crewmembers to monitor its proximity to the standing airplane. However, after passing abeam the standing airplane's empennage and observing the wing walker's "all clear signal," the first officer redirected his attention toward their new course and away from the standing airplane's left wing.

Due to a lack of available ground area, and to accommodate the airport's need for additional airplane movement areas, the FAA had approved a reduction in clearance between the terminal gates and the adjacent taxiway/taxilane. Airport management was aware of the collision hazard related to the proximity between taxilane "C" and adjacent terminal gates. During the previous 5-year-period, three other collisions had occurred between Boeing 747 airplanes on the taxilane.

TBIT airport management personnel were responsible for enforcing published airport rules that required the arriving Boeing 747 SP-44 (F-GTOM) to power into gate 101, which was equipped with an operative docking light guidance system. However, this guidance system had not been used by the contract ground service company for several years. The TBIT management personnel failed to enforce the policy and allowed the ground service personnel to stop the arriving F-GTOM short of gate 101 thus partially blocking taxilane "C." The ground personnel, using their outdated airport rules manual (that directed a tow-in procedure), planned to utilize a tow tractor to pull the airplane the remaining distance to the gate. This was contrary to the revised manual, which required a power-in procedure. Airport management had failed to ensure that all manual holders were using updated versions of the manual.

Probable cause

Airport management's failure to ensure that its current operating procedure, which required the arriving airplane to power into the terminal gate, was being used. Also causal was (1) the ground service company's utilization of an outdated arrival procedure that directed the arriving airplane to stop short of the gate, thereby obstructing the taxilane; and (2) the ground service company's utilization of a nonstandard marshalling hand signal which was, accordingly, misinterpreted by the departing airplane's crew. A contributing factor was the departing airplane's first officer's misjudged evaluation of wing tip clearance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99FA218
Event ID
20001212X19017
Case number
LAX99FA218
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1999-06-07.
  • API snapshot SHA-256: f68b7c24c48280ca7a89d9b0ccd8891e983f9658566f13a2c7d168ea583840a2; retrieved 2026-09-18T16:56:15.313Z.