Philippine Airlines Flight 110
Airbus Industrie 330-301 · Incident: in flight collision with object on approach
From Ninoy Aquino International Airport (MNL) to Antonio B. Won Pat International Airport (GUM)
Event
- NTSB case
- OPS03IA001
- 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
- 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
- Instrument Meteorological Cond
Airbus Industrie 330-301
- Aircraft type
- Airbus 330
- 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-OHZO
- Operator
- Philippine Airlines
- Onboard fatalities
- Unknown
- Route
- From Ninoy Aquino International Airport (MNL), ManilaTo Antonio B. Won Pat International Airport (GUM), Agana
- 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
- Approach · IFR initial approach
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Atc personnel(artcc) › Safety advisory, not issued
- Flightcrew › Proper glidepath, not attained
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
The Philippine Airlines Airbus A330 began an instrument landing system (ILS) approach to runway 6L at A.B. Won Pat Guam International Airport. According to flight data recorder information and the captain's statement, the captain set the autopilot to fly a 3.4 degree descent angle as the aircraft descended through 3,600 feet. At that point, the aircraft was 12.7 miles from the runway 6L touchdown point, where the calculated glideslope height based on the 3.0 degree glideslope specified on the ILS 6L approach chart is 4,060 feet. Therefore, the aircraft began its approach from a position 460 feet below the glideslope at an angle that was 0.4 degrees steeper than the standard glideslope. This resulted in a descent path that ended at the top of Nimitz Hill, approximately 4.5 miles from the runway 6L touchdown point. The airplane struck power lines at the hilltop, which is located about one mile from the site of a fatal accident involving a Korean Airlines (KAL) Boeing 747 that occurred in 1997. The crew then responded to a ground proximity warning system(GPWS) alert and began a climb, returning for another approach. The Guam air traffic control radar system generated a minimum safe altitude warning (MSAW) alert to the radar controller at 17:34:25 that continued for 1 minute and 22 seconds and ended at 17:35:47. During this period, the aircraft descended from approximately 1,700 feet to approximately 700 feet, and then began climbing in response to the GPWS alert. The controller took no action to warn the crew or the GUM tower controller about the aircraft's MSAW alert status or proximity to terrain. After the 1997 KAL accident, the Safety Board recommended that the FAA consider designating Guam International Airport as a special airport requiring special pilot qualifications. At this time, that recommendation is classified as "Open - Acceptable Action" by the Safety Board.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record OPS03IA001
- Event ID
- 20030131X00137
- Case number
- OPS03IA001
- 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. 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: aa10567c368e64262256e61b6d539bcde29b0c4f9b3b263e43bc2300f167b8da; retrieved 2026-09-18T15:56:33.618Z.