![]()  | 
            37000 Feet | Browse and search NASA's Aviation Safety Reporting System  | 
            
                
  | 
        
| Attributes | |
| ACN | 715540 | 
| Time | |
| Date | 200611 | 
| Local Time Of Day | 1801 To 2400 | 
| Place | |
| Locale Reference | airport : dtw.airport | 
| State Reference | MI | 
| Altitude | agl single value : 0 | 
| Environment | |
| Light | Night | 
| Aircraft 2 | |
| Operator | common carrier : air carrier | 
| Make Model Name | Regional Jet CL65 Undifferentiated or Other Model  | 
| Operating Under FAR Part | Part 121 | 
| Flight Phase | ground : taxi | 
| Flight Plan | IFR | 
| Person 1 | |
| Affiliation | company : air carrier | 
| Function | other personnel | 
| ASRS Report | 715540 | 
| Person 2 | |
| Affiliation | company : air carrier | 
| Function | flight crew : captain oversight : pic  | 
| Events | |
| Anomaly | incursion : taxiway non adherence : company policies non adherence : published procedure other anomaly other  | 
| Independent Detector | other other : 1 | 
| Resolutory Action | none taken : anomaly accepted | 
| Supplementary | |
| Problem Areas | Environmental Factor Company Airport  | 
| Primary Problem | Airport | 
| Situations | |
| Airport | markings : dtw.airport | 
Narrative:
I am a ramp control person for air carrier #1. It is my duty to give pushback and taxi clearance for aircraft in a non-movement area determined by ATC. Air carrier #2 (call sign inaudible) called my frequency at dtw for push clearance from gate. I was controling gate X from a different terminal. They were immediately advised to contact ATC/ground for push clearance. This is the second call by air carrier #2 for push clearance on wrong frequency. Approximately 2 weeks prior; I had received a push clearance call from gate X and what I thought was air carrier #3; and accidentally gave instructions for push for air carrier #2 into an ATC controled area. ATC was promptly called when error was realized. I believe that having 2 gates with the same concourse and gate number at the same airport is capable of creating an unnecessary incident. As well as the fact that air carrier #2 does not have the proper frequency information.
Original NASA ASRS Text
Title: RAMP CTLR EXPRESSED CONCERN THAT TWO GATES HAVING THE SAME CONCOURSE AND GATE NUMBER AT DTW COULD LEAD TO A GND INCIDENT.
Narrative: I AM A RAMP CTL PERSON FOR ACR #1. IT IS MY DUTY TO GIVE PUSHBACK AND TAXI CLRNC FOR ACFT IN A NON-MOVEMENT AREA DETERMINED BY ATC. ACR #2 (CALL SIGN INAUDIBLE) CALLED MY FREQ AT DTW FOR PUSH CLRNC FROM GATE. I WAS CTLING GATE X FROM A DIFFERENT TERMINAL. THEY WERE IMMEDIATELY ADVISED TO CONTACT ATC/GND FOR PUSH CLRNC. THIS IS THE SECOND CALL BY ACR #2 FOR PUSH CLRNC ON WRONG FREQ. APPROX 2 WKS PRIOR; I HAD RECEIVED A PUSH CLRNC CALL FROM GATE X AND WHAT I THOUGHT WAS ACR #3; AND ACCIDENTALLY GAVE INSTRUCTIONS FOR PUSH FOR ACR #2 INTO AN ATC CTLED AREA. ATC WAS PROMPTLY CALLED WHEN ERROR WAS REALIZED. I BELIEVE THAT HAVING 2 GATES WITH THE SAME CONCOURSE AND GATE NUMBER AT THE SAME ARPT IS CAPABLE OF CREATING AN UNNECESSARY INCIDENT. AS WELL AS THE FACT THAT ACR #2 DOES NOT HAVE THE PROPER FREQ INFO.
Data retrieved from NASA's ASRS site as of January 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.