Date: 201701
Local time of day: 1801-2400
Location: ZJX.ARTCC, FL
Operator: Air Taxi
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Second aircraft: Widebody; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Anomaly: ATC Issue All Types; Inflight Event / Encounter Other / Unknown
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Company Policy; Airspace Structure; Procedure
Primary problem: Procedure

Narrative: I was working R52/51. ZDC sector 09 initiated a handoff on Aircraft X heading southbound at FL410 which is an Inappropriate Altitude for Direction of Flight (IAFDOF). Instead of calling on the land line and APREQing Aircraft X wrong for direction; 09 left Aircraft X at FL410 and continued to initiate a handoff. The aircraft was less than 30 seconds from the sector boundary and ZDC 09 still had not even called for a handoff. I got on the land line and shouted 'Sector 09; Aircraft X is approved wrong for direction' and took the hand off on Aircraft X. The controller at ZDC Sector 09 clearly had no intention of coordinating Aircraft X as IAFDOF and never had any intention of calling for a handoff. Had I not taken the handoff; there would have been a separation error with Aircraft X entering my airspace without a handoff.I informed my supervisor of the issue (there ended up being two issues with the same controller at ZDC Sector 09; which I have filed an additional ATSAP on) and my supervisor called ZDC to discuss the issue. When my supervisor indicated to whomever he spoke with on the phone at ZDC that the controller at ZDC Sector 09 had not coordinated the IAFDOF the person on the phone at ZDC basically said big deal who cares. I did not hear the phone call; rather; this is what my supervisor told me after he got off the phone with ZDC.I recommend that in the future the controller at ZDC Sector 09 follow the 7110.65 and comply with the rules and regulations that we are expected to work by. In the future; the ZDC Sector 09 controller should coordinate IAFDOF aircraft with the adjacent sector/facility.


Second narrative: I was working Sector 09 when I noticed an aircraft at the northern end of my sector going southbound into JAX a/s over the water; Aircraft Y; appeared to have a bad route. I was not aware of the correct route. So I called JAX gave them the CID (Computer Identification) and said something to the effect; I do not think that looks like good route. What do you think? The response I got was no; it will take him through Sea Lords a/s. So I asked what do you suggest? What can I give him? The JAX controller said; the right route with serious attitude. Not sure what else was said but I politely responded and got off the line. I then asked some fellow controllers in the area what they thought. Everyone was not sure and thought PANAL or something similar would work and give JAX the opportunity to correct it. I was not satisfied so called TMU to ask for a route. TMU also said PANAL looked very similar and looked good. I felt PANAL was not far enough to the south so I gave the a/c OLDEY. In the process of dealing with all of this I also had an a/c Aircraft X that was at FL410 southbound wrong for direction that I had every intention on getting down. There was also [a situation] taking place behind me; a military flight. Breaking up; climbing to FL430 entering my a/s. I told the controller he was p/o approved with me. Mean while and unfortunately Aircraft X had already started to auto flash to JAX. About 3 to 4 miles from the JAX boundary JAX takes radar and shouts over the land line Aircraft X FL410 wrong way is approved. Then eventually Aircraft Y [made] his way down to the south and I start to flash the h/o around DIW. JAX calls about 3 mins from the boundary and says; that routing is still wrong. I said he's your control. He says; I'm not taking that h/o till you get the right route in. I say; I talked to my TMU they said they do not have other routing and that routing looks good. I believe you said some other things but of course at this point with everything going on I say is he p/o approved till I get this route in and he says yes. I call TMU they say ok. I also tell my sup. The a/c gets a good 20 miles into JAX a/s. TMU calls me back says supposedly we are suppose to have reroutes for the military a/s for these guys and we don't. TMU said they have coordinated and worked it out with their TMU and someone will be walking down to the area and they will be taking the h/o. Eventually JAX does take the h/o. Also when I told 34/50 I would take a p/o on the EMRG it made that situation that much more difficult for them and ILM/35 to deal with. The military flight ended up splitting and there was a lot going on in the area at one time. While I was trying to talk to the sup about the situation he was dealing with the [situation].With everything that took place I feel we should be bigger and better than the pettiness that was displayed. I tried to coordinate. I tried to reach out and discuss. Unfortunately it turned into something else. I understand our job is stressful and sometime we do get fed up. But; we get compensated graciously for it. I know I would have never done what the JAX controller chose to do but that is his right. I feel it all could have been prevented and could have worked out much differently. I have learned a valuable lesson and will correct the situation.


Synopsis: 2 ARTCC Controllers from different Centers' reported a situation where an aircraft checked on frequency on an unapproved altitude for their direction of flight.  In addition the ZDC Controller reported the handoff was not being taken by ZJX due to an improper route which was later amended by the TMUs of both ZDC and ZJX.