Wrench978
Pre-takeoff checklist
- Joined
- Nov 27, 2014
- Messages
- 383
- Location
- San Juan, Puerto Rico
- Display Name
Display name:
Wrench978
I’ll add my perspective to the mix. At my center, we use Micro-EARTS. To add a VFR flight plan to the FDIO, I have to hit the “VFR flight plan” key, type your callsign with a Z in front (ZN4254B- that is how we identify VFR flights locally) then the aircraft type and route of flight which is 2 3 letter IDs separated by a splat. So an example would be “VP ZN4254B BE35 BQN*SIG”. That would give us a code to issue to the pilot. I don’t care about what altitude you’re climbing to as much as other places do. If you look like you’re going to conflict with someone, I’ll ask. I can’t validate your Mode C (the reason for saying your current altitude) until you’re tagged up, which could take a minute or 2, so I would prefer not saying altitude until I ask (N4254B, radar contact 8 miles east of BQN, say altitude). If you gave me your altitude on initial call up, you will have likely climbed more than the 300 foot buffer we are allowed.
I understand that the way we do things in San Juan is different than in most of the US. So take all that with a grain of salt.
Also, you don’t have to spell airports for the controllers unless it’s far away. We get paid to know those things. Especially if it’s within the same facility.
I understand that the way we do things in San Juan is different than in most of the US. So take all that with a grain of salt.
Also, you don’t have to spell airports for the controllers unless it’s far away. We get paid to know those things. Especially if it’s within the same facility.