If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
Actions
FOKKER F50
From SKYbrary Wiki
F50
Aircraft | ||||||
---|---|---|---|---|---|---|
Name | F50 | |||||
Manufacturer | FOKKER | |||||
Body | Narrow | |||||
Wing | Fixed Wing | |||||
Position | High wing | |||||
Tail | Regular tail, high set | |||||
WTC | Medium | |||||
APC | B | |||||
Type code | L2T | |||||
Engine | Turboprop | |||||
Engine count | Multi | |||||
Position | (Front) Wing leading mounted | |||||
Landing gear | Tricycle retractable | |||||
Mass group | 3 | |||||
|
FOKKER F50
Description
Technical Data
Wing span | 29 m95.144 ft <br /> |
---|---|
Length | 25.2 m82.677 ft <br /> |
Height | 8.4 m27.559 ft <br /> |
Powerplant | 100: 2 x 2.500 SHP P&W PW125B turboprops with 6 blade propellers.
300: 2 x 2.750 SHP P&W PW127B turboprops with 6 blade propellers. |
Engine model | Pratt & Whitney Canada PW100 |
Performance Data
Take-Off | Initial Climb (to 5000 ft) |
Initial Climb (to FL150) |
Initial Climb (to FL240) |
MACH Climb | Cruise | Initial Descent (to FL240) |
Descent (to FL100) |
Descent (FL100 & below) |
Approach | ||||||||||
V2 (IAS) | 120 kts | IAS | 130 kts | IAS | 210 kts | IAS | 210 kts | MACH | TAS | 240 kts | MACH | IAS | 220 kts | IAS | kts | Vapp (IAS) | 120 kts | ||
Distance | 1100 m | ROC | 1500 ft/min | ROC | 1000 ft/min | ROC | 1000 ft/min | ROC | ft/min | MACH | ROD | ft/min | ROD | 1500 ft/min | MCS | 170 kts | Distance | 1100 m | |
MTOW | 2082020,820 kg <br />20.82 tonnes <br /> kg | Ceiling | FL250 | ROD | ft/min | APC | B | ||||||||||||
WTC | M | Range | 15001,500 nm <br />2,778,000 m <br />2,778 km <br />9,114,173.235 ft <br /> NM |
Accidents & Serious Incidents involving F50
- A320 / F50, Adelaide Australia, 2016 (On 17 August 2016, a Fokker F50 crossed an active runway at Adelaide ahead of an A320 which was about to land after both its pilots and the controller involved had made assumptions about the content of radio transmissions they were aware they had not fully heard. The Investigation found that the A320 crew had responded promptly to the potential conflict by initiating a low go around over the other aircraft and noted that stop bars were not installed at Adelaide. In addition, aircraft taxiing across active runways were not required to obtain their crossing clearances on the runway control frequency.)
- F50 / P28T, vicinity Friedrichshafen Germany, 2016 (On 21 April 2016, a Fokker F50 under radar control in Class ‘E’ airspace was almost in collision with a VFR Piper PA28 after they closed on a constant relative bearing when inbound to Friedrichshafen in VMC. After only being able to locate the PA28 on their TCAS display, the F50 crew implemented a lateral avoidance manoeuvre which prevented generation of an RA. The Investigation concluded that special ATC procedures in place due to busy traffic because of an annually-held trade fair at Friedrichshafen had entailed “systemic risk” and also identified inadequate controller coordination as contributory to a near collision.)
- F50 / T6, vicinity Maastricht Netherlands, 2007 (On 2 August 2007, a Fokker F50 on an ILS approach to Maastricht in IMC came into close proximity inside the CTZ with an unseen light aircraft which had failed to comply with its Special VFR transit clearance. The Investigation found that the transiting aircraft had come within 0.14nm / 260 metres of the opposite direction F50 at a similar altitude without either aircraft having sight of the other, and that the Harvard had been wrongly assumed by ATC to be a helicopter after an initial lack of call sign prefix clarity on first contact had not been positively resolved.)
- F50, Groningen Netherlands, 2007 (On 18 May 2007, a Fokker 50 being operated by Belgian airline VLM on a passenger flight from Amsterdam to Groningen landed long and at excessive speed after a visual day approach to runway 05 at destination and ran off the end of the runway onto grass. None of the 14 occupants were injured and the aircraft suffered only minor damage with two runway lights being damaged.)
- F50, Isle of Man, 2009 (On 15 January 2009 a VLM Fokker 50 left the side of the runway at the Isle of Man during the daylight landing roll. It was concluded that directional control had been lost on the wet runway because the crew had attempted rudder steering whilst also applying reverse pitch, an action which was contrary to SOPSs.)
- F50, vicinity Luxembourg, 2002 (On 6 November 2002, a Fokker 50 operated by Luxair, crashed on approach to Luxembourg Airport following loss of control attributed to intentional operation of power levers in the ground range, contrary to SOPs.)
- F50, vicinity Nairobi Kenya, 2014 (On 2 July 2014, a Fokker 50 fully loaded - and probably overloaded - with a cargo of qat crashed into a building and was destroyed soon after its night departure from Nairobi after failing to climb due to a left engine malfunction which was evident well before V1. The Investigation attributed the accident to the failure of the crew to reject the takeoff after obvious malfunction of the left engine soon after they had set takeoff power which triggered a repeated level 3 Master Warning that required an automatic initiation of a rejected takeoff.)