 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier X penetrated ZTL airspace from ZDC airspace without radar handoff. Unauthorized airspace entry. Operational deviation.
| Attributes | |
| ACN | 190537 |
| Time | |
| Date | 199109 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : ilm |
| State Reference | NC |
| Altitude | msl bound lower : 35000 msl bound upper : 35000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : ztl artcc : zdc |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | cruise other |
| Route In Use | enroute : direct enroute airway : zdc enroute airway : ztl |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller non radar : 2 controller radar : 2 |
| ASRS Report | 190537 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Events | |
| Anomaly | non adherence : published procedure other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Inter Facility Coordination Failure Operational Deviation |
Narrative:
I was working radar and handoff positions at dixon super hi (at or above FL350) over north carolina with an assistant controller also. This sector had been opened for the first time that day less than 10 min prior, by me. Workload was light to moderate as result of just opening sector, though only working 6 plus/minus airplanes. I noticed air carrier X at FL350, on my sector boundary with ZJX without automated handoff to ZJX sector having been made. I initiated handoff and called sector controller in handoff line. No response, but controller accepted the handoff immediately and I gave air carrier X a frequency change. I believe I overlooked this handoff because I had removed the leader length in air carrier X data tag, for an unknown reason, prior to the incident. This is a common operating method for a controller to keep track of handoffs that have been made in one's sector.
Original NASA ASRS Text
Title: ACR X PENETRATED ZTL AIRSPACE FROM ZDC AIRSPACE WITHOUT RADAR HDOF. UNAUTH AIRSPACE ENTRY. OPDEV.
Narrative: I WAS WORKING RADAR AND HDOF POSITIONS AT DIXON SUPER HI (AT OR ABOVE FL350) OVER N CAROLINA WITH AN ASSISTANT CTLR ALSO. THIS SECTOR HAD BEEN OPENED FOR THE FIRST TIME THAT DAY LESS THAN 10 MIN PRIOR, BY ME. WORKLOAD WAS LIGHT TO MODERATE AS RESULT OF JUST OPENING SECTOR, THOUGH ONLY WORKING 6 PLUS/MINUS AIRPLANES. I NOTICED ACR X AT FL350, ON MY SECTOR BOUNDARY WITH ZJX WITHOUT AUTOMATED HDOF TO ZJX SECTOR HAVING BEEN MADE. I INITIATED HDOF AND CALLED SECTOR CTLR IN HDOF LINE. NO RESPONSE, BUT CTLR ACCEPTED THE HDOF IMMEDIATELY AND I GAVE ACR X A FREQ CHANGE. I BELIEVE I OVERLOOKED THIS HDOF BECAUSE I HAD REMOVED THE LEADER LENGTH IN ACR X DATA TAG, FOR AN UNKNOWN REASON, PRIOR TO THE INCIDENT. THIS IS A COMMON OPERATING METHOD FOR A CTLR TO KEEP TRACK OF HDOFS THAT HAVE BEEN MADE IN ONE'S SECTOR.
Data retrieved from NASA's ASRS site as of July 2007 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.