Incident Overview

Date: Sunday 14 July 1935
Aircraft Type: Fokker F.XXII
Owner/operator: KLM Royal Dutch Airlines
Registration Number: PH-AJQ
Location: near Amsterdam-Schiphol Municipal Airport (AMS) – ÿ Netherlands
Phase of Flight: Initial climb
Status: Destroyed, written off
Casualties: Fatalities: 6 / Occupants: 20
Component Affected: Engines (specifically engine numbers 1 and 2)Engines (specifically engine numbers 1 and 2)
Category: Accident
A four-engined airliner, the Kwikstaart, experienced a catastrophic failure during an international flight from Amsterdam-Schiphol Airport to Malm”, Sweden. Engine failures forced a return to the airport, resulting in a crash on the A4 motorway. The incident involved a fire and suggests potential issues with fuel supply during takeoff.A four-engined airliner, the Kwikstaart, experienced a catastrophic failure during an international flight from Amsterdam-Schiphol Airport to Malm”, Sweden. Engine failures forced a return to the airport, resulting in a crash on the A4 motorway. The incident involved a fire and suggests potential issues with fuel supply during takeoff.

Description

The four-engined airliner named “Kwikstaart” took off from Amsterdam-Schiphol Airport at 09:37 on an international flight to Malm”, Sweden with planned en route stops at Hamburg and Copenhagen. Engines no. 1 and 2 began losing power, forcing the pilot to return to the airport. The airplane struck the slope of the A4 motorway and crashed. A fire erupted. Conclusions: 1) Insufficient fuel supply to the engines during takeoff might have made it necessary to manually pump additional fuel. In very unfavourable circumtances there still may be insufficient fuel pressure. 2) The decision of the pilot to return to the airport instead of carrying out a forced landing.

Primary Cause

Insufficient fuel supply to the engines during takeoff, potentially exacerbated by unfavorable circumstances.Insufficient fuel supply to the engines during takeoff, potentially exacerbated by unfavorable circumstances.

Share on:

Leave a Reply

Your email address will not be published. Required fields are marked *