May 2008 CLT Runway Incursion Update

Does anybody know what CLT tower operating procedures were changed, if any, as a result of this incursion?
 
Does anybody know what CLT tower operating procedures were changed, if any, as a result of this incursion?


They are listed here.


As a result of this runway incursion, CLT air traffic management modified the SOP to assist in preventing a recurrence of this type of incident. In addition to the existing procedures of verbal coordination between the LC and GC for intersection departures and annotation in block 12 of the flight progress strip, GC must obtain approval from LC prior to taxiing a departing aircraft to allocation other than the approach end of the runway for departure. The request shall include the callsign of the aircraft and the specific intersection requested. If the request is approved by the LC, GC shall indicate in block 12 of the associated flight progress strip the intersection from which the aircraft will be departing and circle block 12 in red. Additionally, the GC shall place a memory aid, which is a flight progress strip with the word "intersection" in bold letters, in the flight progress strip queue prior to each aircraft that is assigned a departure location other than the approach end of the runway.
To prevent mis-identification of aircraft taxiing outbound for departure the GC is now required to ensure that aircraft are properly tagged on the ASDE-X. If aircraft cannot properly tag on the ASDE-X, GC shall inform the LC who will be working the aircraft.
 
Back
Top