Common processes Flashcards
AFIL
- ABC squawk ident and pass details
- Note details on scratch pad. Callsign, rego, RFL, FRUL, type, route, ADES, equipment
- Create FPL. ADEP will be AFIL, ETD some time in future
- Type the route or use CRTE function and right click on final point to finish
- EST the plan, issue the squawk code
- Identify and verify
- Clearance, traffic, QNH as appropriate
Remember: “ABC call me back in X minutes” if under the pump
Mode C out of tolerance (> +/-200ft)
- ABC check altimeter setting and confirm level, [QNH]
- If still out and aircraft on climb, request aircraft report once maintaining
- If still out and maintaining – “ABC stop squawk Charlie, wrong indication”
- Input P[level] in label
- Use pilot reported and CFL cross-referenced to separate
Transponder unserviceable
- Advise aircraft identification terminated
- Apply procedural separation – vertical is best; can you push OCTA to avoid the need to separate?
- Instruct aircraft to “recycle transponder [code]”
- If still nothing, ascertain if secondary transponder equipped – if so, activate
- If still nothing, set PETOs and obtain position reports
- TSPR US in label
- Coord to SM and affected sectors/units
PJE overhead IFL
- EST the strip or search callsign through FPL
- Issue squawk code
- Input 0800 delay to strip
- Class C – requires coded clearance. Issue as appropriate re: separation (Whiskey requires coord to CSA)
- Separating chutes and non-PJE in Class C by 7NM, PJE and non-PJE by 5NM
- Issue clearance to drop, block level CFL
- Can use “not below parachutists” if running non-PJE over the top (NBP in label)
PJE in Class E (overhead DKI, TUY)
- EST the strip or search callsign through FPL
- Issue squawk code
- Input 0800 delay to strip
- Class E – clearance for IFR, not for VFR. Issue accordingly.
- Separation not required between non-PJE and chutes in Class E & G
- Separation required between IFR and IFR in Class E
- Traffic only between IFR and VFR in Class E
- Issue traffic/clearance to drop as approriate, and reciprocate traffic to non-PJE re: chutes
- Can offer vectors to keep non-PJE aircraft clear of chute area
VFR upgrade to IFR
Does the aircraft have a flight plan? If not, create one with I in FRUL from details passed. If yes, follow procedure:
1. DCT aircraft to next point
2. Open flight plan
3. Input IFR after the lat long in the route field
4. Change FRUL to Z
5. “ABC operate IFR, cleared to [ADES] via [point], FPR, [level]
IFR downgrade to VFR
- DCT aircraft to next point
- Open flight plan
- Input VFR after lat long in route field
- Change FRUL to Y
- “ABC IFR cancelled, operate VFR, identification and control services terminated, squawk 1200, frequency transfer approved, traffic is…”
Note: if VFR operating in Class C, will require a clearance
Flight Following request
- ABC Brisbane Centre, squawk ident and pass details
- Search for FPL (requires one if going to TMA, otherwise RADTAG will suffice), cretae/EST/depart and squawk ASSR
- If RADTAG, get aircraft to squawk ASSR, put SIS in label
- ABC identified, [position], [traffic], [QNH], verify level (service begins now, do not move on without giving QNH and traffic after identifying)
Cancellation:
1. ABC flight following and identification terminated [reason], squawk 1200
2. CFL to NONE, remove SIS from label, inhibit track
Amended destination
- C prompt OFF – consider coord
- (If in CTA) Put on heading that directs them towards requested destination
- RER and coordinate as necessary, C prompt ON
- Issue the clearance (including “resume own nav” if on a heading)
- Contact FDC
Remember – if a level change was requested with amended destination, change the PCLs