mrtennis924

To Clive, My flight plan was set up to go around the TFR so I didn't need to refile it here is the flight plan: KTEB PIYIN COL GXU ACY ILS OR LOC/DME RWY 31 KACY 6000ft. As far as the response unable I don't know how it is outside of the US but here in the US it is one of the most important words that we have in our pilots vocabulary when dealing with ATC . There are many reasons why we may say that one of which is on approach and ATC wants us to speed up to a speed that we're not able to do so we would reply with unable. Altitudes are another reason why we may reply with unable, maybe we just can't climb as high as they want us to or maybe we can't descend as fast as they want us to or we're not comfortable doing something in which case we can reply with unable and ATC must work around that. Tony

Dave, just started using this yesterday and I am really impressed with it. However I do have some issues and I don't know if it's because I have updated nav database or some other problem. One problem was flying X-Plane 11, from Teterboro (KTEB) airport to Atlantic City (KACY) IFR with the flightplan filed. The flight plan was set up in such a way as to go around the TFR in New Jersey because of the president. While flying to my first waypoint west of Teterboro, ATC wanted me to turn south into the TFR I responded with "unable", but they continue to try to turn me into the TFR . The second issue I had was on the return flight from Atlantic City to Republic airport (KFRG) on Long Island via aflight plan taking me north thru New Jersey then across to the JFK VOR to transition to RNAV approach 01 at KFRG. ATC after T/O turned me SSE for miles and never turned me north. Like I said earlier I don't know if the issue is with my Navigraph database 1707 in X-Plane 11, or some other issue. I know there's a new cycle today and I have not downloaded that yet. Also I think ATC should respect a pilots response of "unable". Any help or clarification would be greatly appreciated. Tony