Serious incident Boeing 747-8HVF VQ-BLR, Friday 13 January 2017
ASN logo
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:Friday 13 January 2017
Time:19:23 LT
Type:Silhouette image of generic B748 model; specific model in this crash may look slightly different    
Boeing 747-8HVF
Owner/operator:Air Bridge Cargo
Registration: VQ-BLR
MSN: 37668/1452
Fatalities:Fatalities: 0 / Occupants: 4
Other fatalities:0
Aircraft damage: Unknown
Category:Serious incident
Location:Amsterdam-Schiphol International Airport (AMS/EHAM) -   Netherlands
Phase: Landing
Departure airport:Novosibirsk-Tolmachevo Airport (OVB/UNNT)
Destination airport:Amsterdam-Schiphol International Airport (AMS/EHAM)
Investigating agency: Dutch Safety Board
Confidence Rating: Accident investigation report completed and information captured
AirBridge Cargo flight RU548, a Boeing 747-8HV(F), VQ-BLR, contacted runway threshold lights during landing on runway 36R at Amsterdam-Schiphol Airport, Netherlands.
The aircraft landed at 18:23 UTC in weather conditions that included rainshowers and strong 27 knot winds gusting to 41 knots. There were few Cumulonimbus clouds at 1800 feet.
The following flight, Emirates flight EK149 (Airbus A380-861, A6-EDP), carried out a go around after reporting wind shear on finals.

This aircraft was back in service on January 17.

The hard landing was caused by a high rate of descent. The flare manoeuvre was insufficient to reduce the sink rate satisfactorily.
The fact that the aircraft hit the runway threshold lights was a combination of the continued flight below the glideslope, from the moment the captain disconnected the autopilot at 700 feet and took over the controls manually, and a high sink rate shortly before the touchdown. There was a stable approach until just before the landing. Right before landing two automatic GPWS warnings were generated (“glideslope” and “sink rate”) whereby the stable approach criteria were exceeded. This should have been a reason to make a go-around. However, this was not carried out by the captain, although the procedures required it. According the Operations Manual of Air Traffic Control the Netherlands, ATIS messages should include any reported windshear conditions. Flight crews are hereby made more aware of sudden wind changes and the necessity to make a go-around in case the approach becomes unstable. Air Traffic Control the Netherlands has not been able to demonstrate that the windshear conditions reported by aircraft crews did result in the ATIS being modified.
The measures taken by the operator after the event are necessary to avoid occurrences like hard landings as well as landing short. Those measures underline the importance of adhering to international established guidelines concerning the stabilized approach criteria and the importance of making a go-around when the approach becomes unstable.

Accident investigation:
Investigating agency: Dutch Safety Board
Report number: 
Status: Investigation completed
Download report: Final report


Revision history:

14-Jan-2017 17:42 harro Added
14-Jan-2017 17:43 harro Updated [Narrative]
14-Jan-2017 22:33 Geno Updated [Time, Aircraft type, Registration, Cn, Operator, Nature, Departure airport, Source]
01-Feb-2017 07:46 harro Updated [Source, Narrative]
27-Aug-2018 17:27 harro Updated [Time, Total occupants, Narrative, Accident report, ]
13-Jun-2022 04:52 Ron Averes Updated [Location, Departure airport]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314