![]()  | 
            37000 Feet | Browse and search NASA's Aviation Safety Reporting System  | 
            
                
  | 
        
| Attributes | |
| ACN | 940938 | 
| Time | |
| Date | 201103 | 
| Local Time Of Day | 1801-2400 | 
| Place | |
| Locale Reference | ZDC.ARTCC | 
| State Reference | VA | 
| Aircraft 1 | |
| Make Model Name | B767-400 and 400 ER | 
| Operating Under FAR Part | Part 121 | 
| Flight Phase | Cruise | 
| Route In Use | None | 
| Flight Plan | IFR | 
| Person 1 | |
| Function | Handoff / Assist Trainee  | 
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy  | 
Narrative:
While being trained at R36 (raleigh); a B767 checked onto the frequency at FL310. Not having taken a radar hand off on a B767; I started to search for the sector that he belonged on. When no flight plan information came up in the system; I asked his location and the B767 responded that they were just passing over the rdu VOR at FL310. I then immediately saw the limited data block over rdu. I asked if he was on J209 and they responded in the affirmative. I then called sector 38 and gave them a point out on the limited data tag and that we were trying to figure out where he was going and why we didn't have a flight plan. My instructor then started asking for the flight plan from the B767; and started to input it into the system. My instructor then called back to ZTL to see if they had flight plan information and they said that they did not. A hand off from ZTL would have eliminated this whole problem.
Original NASA ASRS Text
Title: ZDC Controller described a failed hand off event from ZTL; identified when contacted by the aircraft in question and later observing a limited Data Block.
Narrative: While being trained at R36 (Raleigh); a B767 checked onto the frequency at FL310. Not having taken a RADAR hand off on a B767; I started to search for the sector that he belonged on. When no flight plan information came up in the system; I asked his location and the B767 responded that they were just passing over the RDU VOR at FL310. I then immediately saw the limited data block over RDU. I asked if he was on J209 and they responded in the affirmative. I then called Sector 38 and gave them a point out on the limited data tag and that we were trying to figure out where he was going and why we didn't have a flight plan. My instructor then started asking for the flight plan from the B767; and started to input it into the system. My instructor then called back to ZTL to see if they had flight plan information and they said that they did not. A hand off from ZTL would have eliminated this whole problem.
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.