Ariana Afghan Airlines Flight 701
A Boeing 727 similar to Ariana Afghan Airlines Flight 701
|
|
Occurrence summary | |
---|---|
Date | 5 January 1969 |
Summary | Pilot error |
Site | Fernhill Lane, Fernhill, near Horley, Surrey, England Lua error in package.lua at line 80: module 'strict' not found. |
Passengers | 54 |
Crew | 8 |
Injuries (non-fatal) | 15 (1 on ground) |
Fatalities | 50 (2 on ground) |
Survivors | 14 |
Aircraft type | Boeing 727-113C |
Operator | Ariana Afghan Airlines |
Registration | YA-FAR |
Flight origin | Kabul International Airport, Afghanistan |
1st stopover | Kandahar International Airport, Afghanistan |
2nd stopover | Istanbul Atatürk Airport, Turkey |
3rd stopover | Frankfurt Airport, Germany |
Destination | London Gatwick Airport, England |
Ariana Afghan Airlines Flight 701 was the flight involved in a fatal air accident on 5 January 1969, when a Boeing 727 with 62 people on board[1] crashed into a house on its approach to London Gatwick Airport in heavy fog. Due to pilot error the flaps were not extended to maintain flight at final approach speed.
At 0135[note 1] on a Sunday morning on which the Gatwick area was affected by patches of dense freezing fog, Boeing 727 registration number YA-FAR (the only such aircraft in the company's fleet) descended below its correct glide slope as it approached the airport from the east. As it passed over the hamlet of Fernhill on the Surrey/Sussex border, it hit trees and roofs, began to roll and crashed into a field south of Fernhill Lane, Lua error in Module:Convert at line 452: attempt to index field 'titles' (a nil value). short of the runway. It collided with a large detached house, demolished it and caught fire.[5]
Forty-eight passengers and crew died, and two adult occupants of the house were killed when it was destroyed by the impact. A baby in the house survived with minor injuries. The captain, first officer, flight engineer and eleven passengers also survived.
Contents
Location
Fernhill is a hamlet about Lua error in Module:Convert at line 452: attempt to index field 'titles' (a nil value). from the east end of Gatwick Airport's runway[4] and a similar distance south of the nearest town, Horley.[5] Until boundary changes brought it fully into West Sussex (and the borough of Crawley) in 1990,[6] it straddled the Sussex/Surrey border and was in the parish of Burstow.[7][note 2] The two main roads, Peeks Brook Lane and Fernhill Road (named Fernhill Lane at the time of the accident),[11] run south–north and west–east respectively.
The crash site was a field west of Peeks Brook Lane, south of Fernhill Lane and east of Balcombe Road, a B-road[5] which forms the eastern boundary of the airport. Antlands Lane is further to the south.[5] A house called Longfield south of Fernhill Lane was destroyed by the impact.[5][11]
Accident
Flight FG 701 from Kabul International Airport to Gatwick Airport was a weekly scheduled service[11] which stopped intermediately at Kandahar, Istanbul, and Frankfurt. A crew change also took place at Beirut, at which point Captain Nowroz, First Officer Attayee and Flight Engineer Formuly took charge.[12]
Weather in the Gatwick area overnight on 4–5 January 1969 was poor. There was heavy, freezing fog,[5] and no aircraft had landed at the airport since around 1600 the previous day,[13] although the airport remained open.[4] (International regulations require airports to remain open irrespective of ground conditions, in case of emergencies.)[3] The fog had persisted since the previous day, and although it had cleared from most of southeast England some patches remained at Gatwick at a height of no more than 250 feet (76 m).[14] The Captain was given weather reports which indicated that visibility varied between 50 metres (160 ft) and 500 metres (1,600 ft), the air temperature was −3 °C (27 °F) and freezing fog was predominant. Reports for London Stansted Airport (the designated diversionary destination for this flight) and London Heathrow Airport indicated much clearer conditions,[14] and the flight could also have returned to Frankfurt as enough fuel was carried.[12] (The accident report determined that about 9,000 kilograms (20,000 lb) was left when the aircraft crashed.)[15]
As the aircraft approached Fernhill and was within Lua error in Module:Convert at line 452: attempt to index field 'titles' (a nil value). of Gatwick's runway, it clipped the top of some oak trees in the garden of a house called Twinyards[16] on Peeks Brook Lane.[4][17] This was about 500 yards (460 m) from the point of impact on the ground. It then left tyre marks on the roof of the neighbouring house[5] and knocked chimney-pots off the house opposite,[16] a further 264 feet (80 m) on. At this point the aircraft was only 40 feet (12 m) off the ground. It then caught a television aerial and another group of trees, damaging components on the right-side wing. As it started to roll, the aircraft's wheels touched down briefly and it started to rise again. It failed to clear Longfield, a detached house owned by William and Ann Jones[4] which stood 300 yards (270 m) further west, and completely destroyed it.[4][17] One engine landed in the wreckage of the house along with the rear section of the fuselage, while the forward section of the aircraft disintegrated over a 1,395-foot (425 m) trail.[17] The fuel spilt and immediately caught fire, engulfing the fuselage and the wreckage of the house.[11] The Joneses were killed, but their baby survived with minor injuries:[18] the sides of her cot collapsed inwards, "forming a protective tent under one of the engines".[19]
Residents of Peeks Brook Lane were the first to arrive at the crash site and to contact the emergency services.[16] The first call was received at 0138 at Surrey Police's control room, and officers were dispatched from Horley police station. The first officers arrived seven minutes later,[5] soon followed by PC Keith Simmonds of Oxted station[11] who was on traffic duty that night and who saved the injured baby from the wrecked house.[5] The fire services were also summoned at 0138, and vehicles arrived from 0156 onwards. Surrey and Sussex Fire Brigades sent 20 vehicles to the scene, and more were supplied from the airport by the British Airports Authority.[5][20] Board of Trade accident investigators led by George Kelly also went to the scene.[4] Despite a considerable police presence, their efforts were affected by onlookers obstructing them in the narrow lanes. Police blocks were set up at both ends of Fernhill Lane,[18] and other officers were stationed at Antlands Lane diverting traffic away from Balcombe Road.[5]
Aircraft
The Boeing 727 was less than a year old at the time of the accident and was Ariana's only such aircraft.[4] YA-FAR was built in February 1968 and received its American airworthiness certificate on 25 March 1968. On 29 April 1968 it was granted its registration in Afghanistan, and that country issued its own airworthiness certificate on 14 May 1968. At the time of the crash, the aircraft had recorded 1,715 hours of flying time.[15]
Accident investigators from the Board of Trade took the wreckage to a hangar at Farnborough Airport for analysis.[18] Also involved in the investigation were officials from the United States and Afghanistan.[2] A preliminary statement was issued on 17 January 1969,[21] and the full accident report followed in June 1970.[22]
Crew and passengers
Captain Rahim Nowroz, First Officer and co-pilot Abdul Zahir Attayee and Flight engineer Mohammed Hussain Furmuly[23] were injured but survived.[24] The other five crew members were killed.[25] Captain Nowroz qualified as a pilot in 1956, was employed by Ariana the following year as a co-pilot and had flown 10,400 hours since then—including 512 in Boeing 727 aircraft, which he qualified to fly after training in 1968.[23]
There were 54 passengers on board, 43 of whom were killed. The other 11 suffered serious injuries;[26] they had mostly sat in the forward section of the aircraft. Apart from one girl from the United States, all were from Afghanistan, Pakistan and India[27] (especially the Punjab region).[5] There was a mixture of British residents returning after visiting their families and new immigrants.[4]
Aftermath
The emergency services established a temporary triage facility and rescue centre outside Yew Tree Cottage[16] and later an incident room at Horley police station.[5] Survivors were taken into Fernhill House[11] before being transferred to Redhill General Hospital[4] or, in the case of five badly burned people, the McIndoe Burns Unit at East Grinstead Hospital.[11] Two passengers died en route to Redhill General.[4][24] The baby who survived in the wreckage of the house was also taken there[19] suffering from "severe bruising and slight cuts".[18]
The victims' bodies were transferred to the St. John Ambulance Hall at Massetts Road in Horley, where a temporary mortuary was set up. Relatives were then taken there to identify them. Some bodies were so badly burnt that personal effects had to be used to confirm the victim's identity.[18] Other bodies were moved later to the Kenyon's undertakers firm in London.[5] Inquiries into the 50 deaths started within days: the first inquest was that of William and Ann Jones, held at Reigate from 10 January 1969.[11]
Queen Elizabeth II conveyed a message of condolence to Mohammed Zahir Shah, King of Afghanistan.[11] Five police officers, including PC Simmonds, were awarded the Queen's Commendation for Brave Conduct in respect of their "service exceeding the bounds of duty" at the crash site.[5] Also given this award were five local residents and a passenger on the aircraft[28] who returned to the inferno to rescue family members and also put out the flames on another passenger's clothes.[1]
In terms of fatalities, the accident was (and remains as of 2024) the worst in the vicinity of Gatwick Airport. It was the first serious incident at the airport since a crash in February 1959, when a Vickers Viscount operated by Turkish Airlines came down in a wooded area between Rusper and Newdigate, also on the Surrey/Sussex border,[18] killing 14 passengers and injuring the Turkish Prime Minister Adnan Menderes.[29]
Investigation and cause
Investigators found the cause of the crash was pilot error by the captain. His decision to land at Gatwick was an "error of judgment" brought about by the "deceptive nature" of the weather conditions, which were very difficult—although this itself did not cause the accident. Instead, failure to extend the flaps in the correct sequence and at an appropriate speed caused the aircraft to fall below its glide slope,[30] roll to the right in a nose-high attitude, and crash.
The accident report noted that YA-FAR had a full and "serviceable" instrument panel, a working VHF omnidirectional radio range (VOR) system and Instrument landing system (ILS) equipment.[31] "Satisfactory and routine" communication between air traffic control and the aircraft was noted, and the cockpit voice recorder was recovered.[32] There was also a flight recorder unit in the rear of the fuselage, and this was recovered on 6 January[11] and its contents analysed.[33][34]
The Captain's decision to fly to London rather than remain at Frankfurt was not criticised: he could have landed at Heathrow and Stansted, where the weather was clear, instead of Gatwick if he felt conditions were too bad, and the aircraft could even return to Germany if necessary.[35] By the time the aircraft approached Gatwick, the runway visual range was 100 metres (330 ft) according to the latest weather report at 2350 on 4 January, and was not expected to improve that night; furthermore, this reading was confirmed at 0123 and 0127.[12] At the time, British-registered aircraft were not allowed to land at an airport at a time when its runway visual range was lower than its "declared minimum" (Gatwick's was Lua error in Module:Convert at line 452: attempt to index field 'titles' (a nil value).), but foreign aircraft had their own rules and were not subject to British legislation. Ariana Afghan Airlines pilots were instructed not to land when the runway visual range was lower than an airport's declared minimum (although this was not prohibited by law), but they could use their judgment on whether to descend to critical height[note 3] (200 feet (61 m) for this aircraft) and then attempt a landing.[37]
Captain Nowroz "decided that since patchy fog shifts quickly he would make an approach with a view to landing at Gatwick". The accident report stated that because he was relying principally on visual indications as he came in to land, he may have been distracted from his flight-deck duties; and patchy fog in otherwise clear conditions has been known to severely affect the sighting of visual references, sometimes leading to "disastrous errors of judgment".[37]
Nevertheless, Captain Nowroz's decision to approach Gatwick with a view to landing there presented "no undue risk" and did not cause the accident.[37] Instead, the cause was found to be a series of changes to speed, power and flap angle settings which were not in accordance with the airline's operating procedures and which took place in the last 15 miles (24 km) of the approach.[38] At 0128, the aircraft picked up the ILS localiser beam, and the flaps were lowered in three stages as the aircraft's speed reduced. Soon afterwards, as it approached the ILS glideslope beam, its height and speed were reduced further and the undercarriage was extended. Then the Captain saw a light which he mistook for one at the far end of the runway—it was actually on a hill beyond the airport—and the "stabiliser out of trim" warning light came on. This had been faulty earlier in the flight, and the Captain disengaged the autopilot and the automatic glideslope tracker. At 0133, the flap angle was increased; the aircraft then began to fall below the approach slope and was travelling faster than the crew thought. Only when it reached a height of 400 feet (120 m) was an attempt made to gain height, but this happened too late.[12]
The first three flap adjustments took place at higher speeds than recommended in the airline's procedures, although they did not exceed the Boeing 727's limits.[38] The undercarriage was extended at too high a speed, and the next flap adjustment should have been done in two stages. The sudden change of angle caused the nose to pitch downwards and the aircraft to descend more rapidly than was appropriate for the conditions. The Captain and other crew members did not react to this for about 45 seconds, though, until about 300 feet (91 m) from the ground they applied full power and full up elevator to try to bring the aircraft up. The accident report states that during this 45-second period, they may have been preoccupied by looking for visual confirmation of their position, such as the runway lights.[39]
The legislation prohibiting British aircraft from landing when the runway visual range was too short was extended in September 1969 to cover aircraft from all other countries when flying to airports anywhere in the United Kingdom.[37]
See also
Notes
- ↑ All times in this article are in Greenwich Mean Time, as used in the official accident report[2] and in parliamentary discussions about the events.[3] Most contemporary accounts put the events one hour later: for example the crash was said to have occurred at 0235.[4]
- ↑ Ordnance Survey maps dated 1963 and 1973 indicate that the crash site was immediately on the Sussex side of the county boundary, which crossed Fernhill Lane about halfway between Donkey Lane and Peeks Brook Lane. The house demolished in the crash is shown next to the boundary line on the 1963 map,[8] but on the later map only its grounds and former driveway are marked.[9] In 1990, the boundary was moved further east to the eastern edge of the M23, bringing Peeks Brook Lane and all its buildings into West Sussex.[10]
- ↑ This term, introduced in 1951, is defined as "the altitude specified in the [aircraft's] Operations Manual as the minimum height above airfield level to which an approach to land can safely be continued without visual reference to the ground."[36]
References
- ↑ 1.0 1.1 Kelly 1970, §1.14.
- ↑ 2.0 2.1 Kelly 1970, Introduction.
- ↑ 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 4.10 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 5.00 5.01 5.02 5.03 5.04 5.05 5.06 5.07 5.08 5.09 5.10 5.11 5.12 5.13 5.14 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
- ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 11.0 11.1 11.2 11.3 11.4 11.5 11.6 11.7 11.8 11.9 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 12.0 12.1 12.2 12.3 Kelly 1970, §1.1.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 14.0 14.1 Kelly 1970, §1.7.
- ↑ 15.0 15.1 Kelly 1970, §1.6.
- ↑ 16.0 16.1 16.2 16.3 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 17.0 17.1 17.2 Kelly 1970, §1.12.
- ↑ 18.0 18.1 18.2 18.3 18.4 18.5 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Kelly 1970, §1.13.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Kelly 1970, §3.
- ↑ 23.0 23.1 Kelly 1970, §1.5.
- ↑ 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Kelly 1970, §1.3.
- ↑ Kelly 1970, §1.2.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ The London Gazette: no. 44913. p. 8214. 7 August 1969. Retrieved 14 March 2013.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Kelly 1970, §2.2 (a).
- ↑ Kelly 1970, §1.8.
- ↑ Kelly 1970, §1.9.
- ↑ Kelly 1970, §1.11.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Kelly 1970, §2.1 (a).
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 37.0 37.1 37.2 37.3 Kelly 1970, §2.1 (b).
- ↑ 38.0 38.1 Kelly 1970, §2.1 (c)(i).
- ↑ Kelly 1970, §2.1 (c)(ii).
Bibliography
- Lua error in package.lua at line 80: module 'strict' not found.
External links
- "Air Transport: Ariana Accident: First Findings". Flight International, 23 January 1969. pp. 127–128.
- Aviation Safety Network – Accident description
- Airdisaster.com
- "Picture of YA-FAR – Boeing 727-113C aircraft" – Airliners.com
- "Report on the Accident to Boeing 727-112C YA-FAR 1.5 miles east of London (Gatwick) Airport on 5th January 1969" – Gatwick Aviation Society
- "Fatal Plane Crashes and Significant Events for the Boeing 727" – airsafe.com
- "Aircraft Accident, Gatwick", HC Deb 20 January 1969 vol 776 cc40-4 – Hansard
- "Gatwick – Boeing Crash 1969" – British Pathe
- "Accident details" – planecrashinfo.com
- "Photo of the crashed aircraft" – airdisaster.com
- Cockpit Voice Recorder transcript and accident summary
- "England Plane Crash Said Pilot Error" – The Evening Independent – 6 Jan 1969
- Articles with dead external links from May 2015
- Use British English from May 2011
- Use dmy dates from July 2014
- Aviation accidents and incidents in 1969
- Aviation accidents and incidents in England
- Accidents and incidents involving the Boeing 727
- Airliner accidents and incidents caused by weather
- Airliner accidents and incidents involving fog
- Ariana Afghan Airlines accidents and incidents
- 1969 disasters in the United Kingdom
- 1969 in England
- Disasters in Surrey
- Disasters in Sussex
- Transport in Surrey
- Transport in West Sussex