ASN logo
ASN Wikibase Occurrence # 147093
Last updated: 26 April 2019
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:17-DEC-2002
Time:03:35
Type:Silhouette image of generic A333 model; specific model in this crash may look slightly different
Airbus A330-301
Owner/operator:Philippine Air Lines
Registration: F-OHZO
C/n / msn: 188
Fatalities:Fatalities: 0 / Occupants: 115
Other fatalities:0
Aircraft damage: Minor
Location:near Guam-A.B. Won Pat International Airport (GUM) -   Guam
Phase: Approach
Nature:International Scheduled Passenger
Departure airport:Manila-Ninoy Aquino International Airport (MNL)
Destination airport:Guam-A.B. Won Pat International Airport (GUM)
Narrative:
The Airbus struck pole-mounted electrical transmission cables on Nimitz Hill during a localizer approach to runway 06L at Guam in IMC. The aircraft executed a missed approach and landed safely at Guam. After arriving back at Manila the aircraft was inspected and found to have minor damage to the fuselage and landing gear. On August 6, 1997 an accident happened on the same hill when a Korean Air Boeing 747-3B5 collided with terrain while on approaching runway 06L. The MSAW (minimum safe altitude warning) software which was not functioning properly in 1997 was working fine this time. But the CERAP controller, who was no longer in direct communication with PAL110, did not advise the Agana tower controller of the warning. The warning was displayed in the control tower as well, however, the display was logged as out of service because of damage from a typhoon that struck Guam nine days earlier, and its operation was not verified as reliable.
PROBABLE CAUSE: "The pilot's initiation of a premature descent that was both below the nominal glideslope and steeper than normal. Contributing to the incident was the air traffic controller's failure to respond to the MSAW warning and issue a safety alert as required by FAA order."

Sources:

NTSB


Revision history:

Date/timeContributorUpdates
26-Jul-2012 07:20 harro Added

Corrections or additions? ... Edit this accident description