Boeing 767 34AF N342UP
12 April 2015 · Miami, Florida, United States · Unknown
Summary
On 12 April 2015 at about 12:21 local time, a Boeing 767 34AF registered N342UP, operated by United Parcel Service, was involved in an incident near Miami, Florida, United States. The number of people on board was not recorded. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 12:21
- Classification
- Incident
- Location
- Miami, Florida, United States
- Nearest airport
- Miami Intl (MIA)
- Coordinates
- 25.7953, -80.2900
- Aircraft
- Boeing 767 34AF
- Registration
- N342UP
- Category
- Airplane
- Year built
- 2011
- Engines
- 2
- Operator
- United Parcel Service
- Operating rule
- Part 121: Air Carrier
- Phase of flight
- Not recorded
- Route
- Managua → Miami
- Aircraft damage
- Not recorded
- Weather
- VMC
- Light
- Day
- NTSB number
- OPS15IA017
People
Injuries not recorded.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| Not recorded | 0 | 0 | 0 | 0 |
Probable cause
The controller's issuance of a landing clearance to an arriving aircraft while another aircraft was in position on the same runway. Contributing to the incident was the controller's non-compliance with traffic advisory procedures, and insufficient requirements for use of memory aids to track arrival and departure operations.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
This loss of required air traffic control separation resulted from the LN/LS controller issuing a landing clearance to UPS357 to a runway occupied by N900QS in position on the same runway. This resulted in UPS357 overflying N900QS by about 475 feet. Contributing to the error was the local controller's non-compliance with traffic advisory procedures, and insufficient requirements for use of memory aids to track arrival and departure operations. When issuing a landing clearance to UPS357, the local controller did not ensure the runway was clear as required by FAA Order 7110.65, Air Traffic Control, paragraph 3-10-3, Same Runway Separation and, the local controller did not advise UPS357 that an aircraft was in position on the landing runway as required by FAA Order 7110.65, paragraph 3-10-5c, Landing Clearance. Contributing to this incident was the lack of required memory aids for arrivals. Miami Air Traffic Control Tower procedures required controllers to use memory aids to indicate that an aircraft had been directed to line up and wait (LUAW), when an aircraft was issued a departure clearance, and to indicate that a runway was occupied by an airport vehicle. However, flight progress strips or memory aids were not required for arrivals and arrival flight progress strips were not used. The data available via the radar presentation on the tower display workstation (TDW) was the only information used for arrival sequencing. While the LUAW memory aide is beneficial to prevent a controller from issuing a takeoff clearance for a runway that is occupied by an aircraft in LUAW position, it did not prevent the controller from issuing a landing clearance to UPS357 nine seconds after he had directed N900QS to LUAW. There were no visual aids utilized to indicate an aircraft was on the runway to which an aircraft had also been cleared to land. According to controller interviews, the "rule of thumb" or unofficial procedure for arrivals to a runway occupied by an aircraft in position was that if the arrival reached two miles and the aircraft in position had not started departure roll, the arriving aircraft would be sent around. However, there were no visual clues or memory aids to remind the controller that an aircraft was in position on the runway except where a controller may decide to write down call-signs of arriving aircraft at the control position.
Quoted verbatim from the NTSB record.
Aircraft involved
| Aircraft | Registration | Operator | Damage |
|---|---|---|---|
| Boeing 767 34AF 34AF | N342UP | United Parcel Service | - |
| Cessna 750 NO SERIES | N900QS | Netjets Sales Inc | - |
Other Boeing 767 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 12 Jul 2015 | Boeing 767-346 | Singapore, Singapore | Japan Airlines | Unknown | - |
| 15 Feb 2015 | Boeing 767 | Honolulu, United States | United Air Lines Inc | Serious injuries | - |
| 29 Jun 2015 | Boeing 767 432ER | Atlanta, Georgia, United States | Delta Air Lines, Inc. | Serious injuries | - |
| 17 Feb 2015 | Boeing 767-204ER | Islamabad, Pakistan, Pakistan | Shaneen Air International | Unknown | - |
| 29 Oct 2015 | Boeing 767 | Fort Lauderdale, Florida, United States | Dynamic International | Serious injuries | - |
| 26 Feb 2016 | Boeing 767 | Domodedovo, Russia | Azurair Airlines | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 3 Apr 2015 | Cessna 182R | Fort Myers, Florida, United States | - | No injuries | - |
| 21 Aug 2015 | Piper PA 18-150 | LaBelle, Florida, United States | LOW & Slow Aviation Ventures LLC | No injuries | - |
| 12 Jan 2015 | Piper PA-28R-200 | Deland, Florida, United States | Skyline Solutions Inc | No injuries | - |
| 2 Jan 2015 | Dayton A Babcock STORM | Eustis, Florida, United States | Lake Hoppers Air Adventures, Inc. | No injuries | - |
| 22 Jul 2015 | Bombardier CL-600-2B16 | West Palm Beach, Florida, United States | - | No injuries | - |
| 23 Jul 2015 | Piper PA-28R-180 | Fort Lauderdale, Florida, United States | SkyEagle Aviation Academy | No injuries | - |