37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 942018 |
Time | |
Date | 201104 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZME.ARTCC |
State Reference | TN |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types |
Narrative:
I was working R30 when gadsden high (gad) in ZTL called me with a point out on an aircraft climbing to ultra high. While I had that controller; I pointed out a B737 even though I did not have track control of him yet. Gad accepted the point out. The B737 was climbing out of birmingham al to the west and was level at 230 but was still not flashing to me. I did something else in the sector and looked back and the B737 was still a limited data block but climbing in my airspace through my altitudes. I am not sure which sector I called first but I called both bhm lo and gad to call radar on the aircraft. At some point in time gad hi had track control according to uret so I called them and asked them what altitude the B737 was climbing to. They responded with; 'didn't bhm coordinate with you.' after a short period of time the track was flashed to me. I called gad again and asked them to switch the aircraft. They informed that they never talked to him. I called bhm lo and they switched the B737 to me. Recommendation; obviously there were some coordination errors occurring during this incident.
Original NASA ASRS Text
Title: ZME Controller described an airspace incursion event when an adjacent controller failed to properly coordinate/hand off an aircraft.
Narrative: I was working R30 when Gadsden High (Gad) in ZTL called me with a point out on an aircraft climbing to ultra high. While I had that Controller; I pointed out a B737 even though I did not have track control of him yet. Gad accepted the point out. The B737 was climbing out of Birmingham AL to the west and was level at 230 but was still not flashing to me. I did something else in the sector and looked back and the B737 was still a limited data block but climbing in my airspace through my altitudes. I am not sure which sector I called first but I called both BHM LO and GAD to call RADAR on the aircraft. At some point in time GAD HI had track control according to URET so I called them and asked them what altitude the B737 was climbing to. They responded with; 'didn't BHM coordinate with you.' After a short period of time the track was flashed to me. I called Gad again and asked them to switch the aircraft. They informed that they never talked to him. I called BHM LO and they switched the B737 to me. Recommendation; obviously there were some coordination errors occurring during this incident.
Data retrieved from NASA's ASRS site as of April 2012 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.