Casualties unknown

Airprox Incident Between IBE3513 and DAL154 Near Geneva (N194DN)

UAC West MILPA, CH

On November 27, 2003, a BOEING B767-300 (registration N194DN) was involved in an aviation accident near UAC West MILPA, CH. Investigators recorded the probable cause as: The crew of IBE3513 mistakenly entered flight level 350 in the FCU altitude window instead of the cleared flight level 340, leading to a loss of vertical separation with DAL154. This summary draws on records from the Swiss Transportation Safety Investigation Board (STSB / SUST).

Sourcesthe Swiss Transportation Safety Investigation Board (STSB / SUST)Primary reportUpdated 2026-10-18Data APIEditorial standards
Aircraft registered N194DN
Aircraft registered N194DN. Photo: Juergen Lehle / CC BY-SA 3.0, via Wikimedia Commons

On November 27, 2003, an Airbus A320 and a Boeing 767 experienced a near miss northwest of MILPA. The A320 crew mistakenly set FL350 instead of the cleared FL340, resulting in a minimum altitude difference of 600 feet.

Incident Overview

On November 27, 2003, at 07:55 UTC, an airprox incident occurred approximately three nautical miles northwest of the MILPA waypoint within the UAC Geneva sector. The event involved Iberia Flight 3513, an Airbus A320 registered as EC-IEF, and Delta Air Lines Flight 154, a Boeing 763 registered as N194DN. Both aircraft were operating scheduled services; Iberia was en route from Frankfurt to Madrid, while Delta was traveling from New York to Venice.

Sequence of Events

At 07:37 UTC, the crew of IBE3513 contacted Swiss Radar Area West and received a clearance to maintain flight level (FL) 330 on route BENOT-MEBAK. Shortly thereafter, the pilot requested a climb to FL350. The controller indicated that FL350 was occupied but assigned FL340 four minutes later. Despite receiving and reading back the clearance for FL340, the crew erroneously entered FL350 into the Flight Control Unit (FCU) altitude window.

At 07:48 UTC, DAL154 contacted the same sector at FL350 and was cleared on route MILPA-ORSUD-SARONNO. The routes of the two aircraft intersected perpendicularly near MILPA. At 07:53 UTC, the STCA (Short Term Conflict Alert) system triggered an alert. Radar data indicated IBE3513 had climbed to FL343, exceeding its assigned level. The controller immediately issued traffic information to both crews. DAL154 initiated a climb to FL355 in response to a TCAS resolution advisory, while IBE3513 descended back to FL340.

Findings and Analysis

Radar traces recorded a minimum horizontal separation of 4.6 nautical miles and an altitude difference of 600 feet between the two aircraft. The investigation revealed that the controller in charge was a trainee under direct supervision, and traffic load was average. The primary cause of the incident was identified as a crew error: the co-pilot of IBE3513 mistakenly set FL350 in the FCU instead of the cleared FL340. The commander reported being distracted by a cabin check for electronic device interference and system circuit-breaker checks, which likely contributed to the failure to monitor the altitude acquisition.

Probable cause

The crew of IBE3513 mistakenly entered flight level 350 in the FCU altitude window instead of the cleared flight level 340, leading to a loss of vertical separation with DAL154.

Frequently asked questions

What happened in the 27 Nov 2003 BOEING B767-300 accident near UAC West MILPA, CH?

On November 27, 2003, an Airbus A320 and a Boeing 767 experienced a near miss northwest of MILPA. The A320 crew mistakenly set FL350 instead of the cleared FL340, resulting in a minimum altitude difference of 600 feet.

What aircraft was involved and where did it happen?

The accident on 27 Nov 2003 involved a BOEING B767-300, registration N194DN, at UAC West MILPA, CH.

What was the probable cause of the accident?

The crew of IBE3513 mistakenly entered flight level 350 in the FCU altitude window instead of the cleared flight level 340, leading to a loss of vertical separation with DAL154.

Investigation report by the Swiss Transportation Safety Investigation Board (STSB / SUST). Original record: https://www.sust.admin.ch/inhalte/AV-berichte/1836_e.pdf. This page is a structured re-presentation; facts and quotes are in the Swiss Transportation Safety Investigation Board (STSB), Switzerland.