GULFPORT, MS (WLOX) - The NTSB says "operational error" by an air traffic controller in Gulfport nearly led to a mid-air collision.
An incident report from the NTSB says the incident took place on June 19, 2011.
The report describes how a small private plane and a 55 passenger regional jet heading to Houston got permission to take off within 16 seconds of each other.
According to the NTSB findings, the Cessna 172 was on runway 18 and about to liftoff, when the air traffic controller told the 55 passenger regional jet it could roll down runway 14.
So, how did two planes get take off clearance just 16 seconds apart? The air traffic controller told investigators, "that from previous experience, he anticipated that the Cessna departing runway 18 would take 3 to 5 minutes to get airborne and the ERJ145 would depart well in advance of the Cessna."
However, within seconds, the two aircraft were airborne. And they reportedly passed in front of each other just 300 feet above the airfield.
The NTSB report says, "The Gulfport control tower local controller cleared two aircraft for takeoff from runways with intersecting departure flight paths without ensuring the first aircraft had passed the flight path intersection prior to clearing the second aircraft for takeoff."
According to the NTSB, "The investigation revealed a number of deficiencies within the ATC facility that contributed to this incident."
Because of the near mid-air collision, managers in the Gulfport control tower will no longer let the air traffic controller work the local control position.
NTSB Identification: OPS11IA673A
Scheduled 14 CFR Part 121: Air Carrier operation of EXPRESSJET AIRLINES INC
Incident occurred Sunday, June 19, 2011 in Gulfport, MS
Probable Cause Approval Date: 01/18/2012
Aircraft: EMBRAER EMB-145EP, registration: N13929
Injuries: 55 Uninjured.
N54120, a Cessna 172, called ready for takeoff on runway 18. The tower local controller (LC) cleared the Cessna for takeoff on runway 18. Sixteen seconds later, (Jet Link) BTA2555/Embraer ERJ145 called ready for takeoff for runway 14. The LC cleared the ERJ145 for takeoff. The departure flight path of runway 18 intersects runway 14. The local controller was working the LC position combined with Ground Control (GC), Clearance Delivery (CD)/Flight Data (FD) and Controller-In-Charge (CIC) positions. The Cessna was airborne crossing taxiway Charlie when the ERJ145 passed through the intersecting flight paths airborne in front of the Cessna. Both aircraft were estimated to be at 300 feet. No traffic was issued to either aircraft by the LC. Closest proximity was estimated to be 0 feet vertically and 300 feet laterally. According to FAA Order 7110.65, Air Traffic Control, paragraph 3-9-8, Intersecting Runway Separation:
a. Issue traffic information to each aircraft operating on intersecting runways.
b. Separate departing aircraft from an aircraft using an intersecting runway, or runways when the flight paths intersect, by ensuring that the departure does not begin takeoff roll until one of the following exists:
1. The preceding aircraft has departed and passed the intersection, has crossed the departure runway, or is turning to avert any conflict.
The National Transportation Safety Board determines the probable cause(s) of this incident as follows:
the Gulfport control tower local controller cleared two aircraft for takeoff from runways with intersecting departure flight paths without ensuring the first aircraft had passed the flight path intersection prior to clearing the second aircraft for takeoff.
No comments:
Post a Comment