A crew cleared for the LLBG RNAV 26 arrival found the RNAV missing from the FMGC. While constructing the arrival; ATC issued a LOW ALTITUDE alert and then a brief 'SPEED; SPEED' warning during final level off looking for the VASI.

Date: 2011-12 · Aircraft: Widebody; Low Wing; 2 Turbojet Eng · Phase: approach

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-published-material-policy

Synopsis

A crew cleared for the LLBG RNAV 26 arrival found the RNAV missing from the FMGC. While constructing the arrival; ATC issued a LOW ALTITUDE alert and then a brief 'SPEED; SPEED' warning during final level off looking for the VASI.

Narrative

During approach preparations into Tel Aviv; it was noted that the FMS did not contain the RNV 26 in the FMS database. This approach is the one used most often into Tel Aviv. Runway 12/30 is closed and could not be used. This forced the flight crew to improvise a visual approach to Runway 26 without any real descent guidance. When the aircraft was on base leg; the Tower called with a low altitude warning. The aircraft was fully configured for landing and slowed to approach speed. As a result of the warning from the Tower and the rising terrain in that area; the aircraft was taken off autopilot and leveled off manually until the VASI lights could be picked up visually. As a result of the level off; the 'Speed; Speed' warning was briefly activated as well. The rest of the approach and landing was uneventful. The main cause was the fact that the proper approach data needed for Tel Aviv was not in the database. The secondary cause was a too rapid descent using a combination of V/S and open descent over rising terrain on base leg. The database should be checked and double checked to make sure the crew has the proper tools to do the job and to avoid these situations all together.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.