![]()  | 
            37000 Feet | Browse and search NASA's Aviation Safety Reporting System  | 
            
                
  | 
        
| Attributes | |
| ACN | 1203319 | 
| Time | |
| Date | 201409 | 
| Local Time Of Day | 1801-2400 | 
| Place | |
| Locale Reference | ZDC.ARTCC | 
| State Reference | VA | 
| Aircraft 1 | |
| Make Model Name | Large Transport Low Wing 2 Turbojet Eng  | 
| Operating Under FAR Part | Part 121 | 
| Flight Phase | Climb | 
| Flight Plan | IFR | 
| Aircraft 2 | |
| Make Model Name | Large Transport | 
| Operating Under FAR Part | Part 121 | 
| Flight Phase | Cruise | 
| Flight Plan | IFR | 
| Person 1 | |
| Function | Enroute | 
| Qualification | Air Traffic Control Fully Certified | 
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 14.5 | 
| Events | |
| Anomaly | Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence  | 
Narrative:
I climbed aircraft X to FL400. Based on aircraft performance; I expected the aircraft to be level by the boundary. There were a lot of deviations and rerouted aircraft in my sector adding a lot to the complexity of the sector. I didn't notice aircraft Y coming northbound at FL390. I switched aircraft X to ZTL. When the conflict alert activated; I saw that the only solution was to turn aircraft Y to the right. I turned 20 right and called the badin sector right away to tell them. I called several times and they never picked up the line. No separation was lost (due to my turn) but I never officially got permission to turn in their airspace.tmu has to come up with better plans than to constantly keep traffic in area 5 when there is weather. The complexity of the sectors go through the roof with their asinine ideas to get traffic through with virtually no restrictions. I was so distracted by the huge departure push over mol that I missed a simple thing.
Original NASA ASRS Text
Title: ZDC Controller reports of a airspace deviation that is caused by flight deviations and traffic workload in the sector.
Narrative: I climbed Aircraft X to FL400. Based on aircraft performance; I expected the aircraft to be level by the boundary. There were a lot of deviations and rerouted aircraft in my sector adding a lot to the complexity of the sector. I didn't notice Aircraft Y coming northbound at FL390. I switched Aircraft X to ZTL. When the conflict alert activated; I saw that the only solution was to turn Aircraft Y to the right. I turned 20 right and called the BADIN sector right away to tell them. I called several times and they never picked up the line. No separation was lost (due to my turn) but I never officially got permission to turn in their airspace.TMU has to come up with better plans than to constantly keep traffic in Area 5 when there is weather. The complexity of the sectors go through the roof with their asinine ideas to get traffic through with virtually no restrictions. I was so distracted by the huge departure push over MOL that I missed a simple thing.
Data retrieved from NASA's ASRS site 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.