ASN Wikibase Occurrence # 194950
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 21 April 2017 |
Time: | 11:05 LT |
Type: | Boeing 777-35RER |
Owner/operator: | Jet Airways |
Registration: | VT-JEW |
MSN: | 35164/660 |
Year of manufacture: | 2007 |
Fatalities: | Fatalities: 0 / Occupants: 358 |
Aircraft damage: | None |
Category: | Serious incident |
Location: | Amsterdam-Schiphol International Airport (AMS/EHAM) -
Netherlands
|
Phase: | Take off |
Nature: | Passenger - Scheduled |
Departure airport: | Amsterdam-Schiphol International Airport (AMS/EHAM) |
Destination airport: | Toronto-Pearson International Airport, ON (YYZ/CYYZ) |
Investigating agency: | Dutch Safety Board |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:Jet Airways flight 9W234 returned to land at Amsterdam-Schiphol International Airport, Netherlands after reports that the aircraft suffered a tail strike on departure.
The Boeing 777-35RER took off from runway 18C at 11:05 LT. About 11:10 the Departure controller radioed that the Tower controller thought that the observed a tailstrike on rotation, but that the runway controller did not notice anything.
About 11:12 the Radar controller cleared the flight to climb to FL240. However, about two minutes later the flight requested permission to stop the climb at FL150. Subsequently a request was made to turn back to Schiphol Airport and to descend. The Rdaar controller issued vectors and cleared the flight down to FL100.
A safe landing was carried out on runway 27 at 12:18 LT.
After landing, it appeared that a tail strike had occurred but that the wear of the tail skid shoe was within limits and no immediate repair was necessary.
The tailstrike was caused by an overrotation of the aeroplane during the takeoff, which was the result of a lower than required airspeed at which the rotation was started. The reason for this was that the actual takeoff weight was higher than the takeoff weight that had been used for the takeoff performance calculation. Due to a human error predominantly caused by time pressure, incorrect load sheet data was supplied to the pilots. Neither the airline’s loading procedures nor the cross check of data by the pilots did prevent the use of the incorrect data for the takeoff performance calculation. The interaction between human performance, the cross check of data by the pilots, the airline’s loading procedures, limited systems integration and operational pressure to meet the planned takeoff time contributed to the takeoff performance calculation with the incorrect data as input.
Furthermore, in this situation of insufficient thrust setting, as a result of the takeoff performance calculation with incorrect entry data, the takeoff was performed without the required safety margins. In case of an engine failure after the decision speed V1, the aeroplane would not have been able to continue the flight safely.
Accident investigation:
|
| |
Investigating agency: | Dutch Safety Board |
Report number: | |
Status: | Investigation completed |
Duration: | |
Download report: | Final report |
|
Sources:
https://www.flightradar24.com/data/flights/9w234#d23204e https://www.onderzoeksraad.nl/en/onderzoek/2354/quarterly-report-aviation-2nd-quarter-2017 Images:
Media:
Revision history:
Date/time | Contributor | Updates |
21-Apr-2017 11:38 |
harro |
Added |
21-Apr-2017 11:40 |
harro |
Updated [Photo, ] |
21-Apr-2017 12:06 |
harro |
Updated [Narrative] |
21-Apr-2017 12:15 |
harro |
Updated [Narrative] |
21-Apr-2017 13:31 |
harro |
Updated [Total occupants, Narrative] |
21-Apr-2017 14:05 |
p3dr0x |
Updated [Country] |
21-Apr-2017 19:58 |
harro |
Updated [Embed code] |
22-Apr-2017 19:58 |
harro |
Updated [Embed code, Damage, Narrative] |
15-Aug-2017 19:51 |
harro |
Updated [Source] |
15-Oct-2020 13:53 |
harro |
Updated [Total occupants, Narrative, Accident report] |
14-Jun-2022 03:08 |
Ron Averes |
Updated [Location] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation