Initial tower contact inbound with discrete squawk code
Posted: Fri Oct 09, 2020 10:06 am
I am trying to reconcile a difference I have experienced with PE vs Real world.
Use case: Flying VFR with a discrete squawk code given from the departure airport (ie flight following) or from approach when inbound to a busy airspace.
Real World
The initial call to tower usually goes like this "Somewhere tower, Skyhawk123AB, 2500" and tower responds "Skyhawk123AB, Somewhere tower, enter left downwind for runway 24"
PE
The initial call to tower usually goes like this "Somewhere tower, Skyhawk123AB, 2500" and tower sometimes responds "Skyhawk123AB, Somewhere tower, say current position"
If I was coming in with 1200 because I didn't request flight following or if the approach controller said "radar services terminated, squawk vfr, frequency change approved" I would expect to give the whole spiel "Somewhere tower, Skyhawk123AB, 18 miles east of the field, inbound with charlie" but not sure why the spiel is needed when you have a discrete code.
I would appreciate any clarity you can provide.
Thanks,
Shane
Use case: Flying VFR with a discrete squawk code given from the departure airport (ie flight following) or from approach when inbound to a busy airspace.
Real World
The initial call to tower usually goes like this "Somewhere tower, Skyhawk123AB, 2500" and tower responds "Skyhawk123AB, Somewhere tower, enter left downwind for runway 24"
PE
The initial call to tower usually goes like this "Somewhere tower, Skyhawk123AB, 2500" and tower sometimes responds "Skyhawk123AB, Somewhere tower, say current position"
If I was coming in with 1200 because I didn't request flight following or if the approach controller said "radar services terminated, squawk vfr, frequency change approved" I would expect to give the whole spiel "Somewhere tower, Skyhawk123AB, 18 miles east of the field, inbound with charlie" but not sure why the spiel is needed when you have a discrete code.
I would appreciate any clarity you can provide.
Thanks,
Shane