April 7, 20179 yr Commercial Member Well, you know the copilots these days. They need more training that we did. Looks like a bug in the readback routine. I'll check it out. Thanks, Dave
April 7, 20179 yr Commercial Member I tried to duplicate the bad copilot behavior, but it just seems to work for me. What airport were you at when this happened. It could have something to do with the available frequencies there. Thanks, Dave
April 7, 20179 yr 6 hours ago, Dave-Pilot2ATC said: I tried to duplicate the bad copilot behavior, but it just seems to work for me. What airport were you at when this happened. It could have something to do with the available frequencies there. Thanks, Dave Glitter Gulch payware KLAS-Las Vegas. The frequency list inside P2A seemed to have all the correct data in it. Captain K-Man FlightBlog Channel: https://www.youtube.com/channel/UCulqmz0zmIMuAzJvDAZPkWQ // Streaming on YouTube most Wednesdays and Fridays @ 6pm CST Brian Navy
April 7, 20179 yr And sometimes atc doesn't recognize my call sign with copilot say it. "Aircraft calling. Call back with call sign." At KPHX Phoenix - Sky Harbor
April 8, 20179 yr I think something changed in the acceptable phrases in 2.2.1.1 causing the "Aircraft calling. Call back with call sign." Before, I used to readback the clearance and say my callsign at the end. If I do that now it only listens to half of my readback. But if I say "Callsign is clear to ..." it then understands the readback and clearance delivery sends me to ground. X-Plane 12 (VR only) - HP Reverb G2 - i5 13600k - ASUS TUF RTX 4090 24GB - ASUS TUF Z790-Plus - Corsair Hydro H115i - Corsair 16GB (2 X 8GB) DDR4 4000 (PC4-32000) C18 1.35V - Samsung 860 EVO SSD 500GB - Windows 11 Pro
Archived
This topic is now archived and is closed to further replies.