2002 Iran Antonov An-140 crash

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Aeromist-Kharkiv Flight 2137
200px
An-140 similar to that involved in the incident
Incident summary
Date 23 December 2002 (2002-12-23)
Summary Multiple crew errors due to insufficient training
Site Near Ardestan, Iran
Passengers 38
Crew 6
Fatalities 44 (all)
Survivors 0
Aircraft type Antonov An-140
Operator Aeromist-Kharkiv
Registration UR-14003
Flight origin Kharkiv International Airport, Ukraine
Destination Isfahan International Airport, Iran

On 23 December 2002, an Antonov An-140 crashed near Ardestan, Iran, killing everyone on board. The crash, with 44 fatalities, killed a number of Russian and Ukrainian aviation specialists. By the day after the crash, it was stated that the flight data recorder had been recovered.

Crash

The aircraft was en route from Kharkiv in Ukraine to Isfahan in Iran, having stopped in Trabzon, Turkey to refuel.[1] It hit high ground on a night-time descent to Isfahan International Airport, killing all on board.[2][3] The passengers, including several Russian and Ukrainian specialists and officials,[1] were headed for the official inauguration of Iran's version of another Antonov plane, the An-140 commuter airliner, which is licensed by the Antonov design bureau. Iranian officials at first said they believed pilot error was the cause of the crash, but later said it was too early to determine what caused the accident. The aircraft's flight data recorder was recovered,[4] a short summary of the report was published on the Flight Global website.[2]

Investigation

The initial investigation into the crash stated that the primary cause was due to "procedural navigation errors by the crew".[2] The Commonwealth of Independent States' Interstate Aviation Committee report concluded that the main causes of the crash were poor crew management, failing to apply approach procedures, and incorrect use of the aircraft's GPS satellite navigation system, in breach of its operational requirements and their rating for its use on approach; failure to use information from other installed navigation equipment; failure to seek an alternative approach when they realised the GPS could not be giving a realistic distance measuring equipment readout.[2][5]

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.