Common processes Flashcards

1
Q

AFIL

A
  1. ABC squawk ident and pass details
  2. Note details on scratch pad. Callsign, rego, RFL, FRUL, type, route, ADES, equipment
  3. Create FPL. ADEP will be AFIL, ETD some time in future
  4. Type the route or use CRTE function and right click on final point to finish
  5. EST the plan, issue the squawk code
  6. Identify and verify
  7. Clearance, traffic, QNH as appropriate

Remember: “ABC call me back in X minutes” if under the pump

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Mode C out of tolerance (> +/-200ft)

A
  1. ABC check altimeter setting and confirm level, [QNH]
  2. If still out and aircraft on climb, request aircraft report once maintaining
  3. If still out and maintaining – “ABC stop squawk Charlie, wrong indication”
  4. Input P[level] in label
  5. Use pilot reported and CFL cross-referenced to separate
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Transponder unserviceable

A
  1. Advise aircraft identification terminated
  2. Apply procedural separation – vertical is best; can you push OCTA to avoid the need to separate?
  3. Instruct aircraft to “recycle transponder [code]”
  4. If still nothing, ascertain if secondary transponder equipped – if so, activate
  5. If still nothing, set PETOs and obtain position reports
  6. TSPR US in label
  7. Coord to SM and affected sectors/units
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

PJE overhead IFL

A
  1. EST the strip or search callsign through FPL
  2. Issue squawk code
  3. Input 0800 delay to strip
  4. Class C – requires coded clearance. Issue as appropriate re: separation (Whiskey requires coord to CSA)
  5. Separating chutes and non-PJE in Class C by 7NM, PJE and non-PJE by 5NM
  6. Issue clearance to drop, block level CFL
  7. Can use “not below parachutists” if running non-PJE over the top (NBP in label)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

PJE in Class E (overhead DKI, TUY)

A
  1. EST the strip or search callsign through FPL
  2. Issue squawk code
  3. Input 0800 delay to strip
  4. Class E – clearance for IFR, not for VFR. Issue accordingly.
  5. Separation not required between non-PJE and chutes in Class E & G
  6. Separation required between IFR and IFR in Class E
  7. Traffic only between IFR and VFR in Class E
  8. Issue traffic/clearance to drop as approriate, and reciprocate traffic to non-PJE re: chutes
  9. Can offer vectors to keep non-PJE aircraft clear of chute area
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

VFR upgrade to IFR

A

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]

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

IFR downgrade to VFR

A
  1. DCT aircraft to next point
  2. Open flight plan
  3. Input VFR after lat long in route field
  4. Change FRUL to Y
  5. “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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Flight Following request

A
  1. ABC Brisbane Centre, squawk ident and pass details
  2. Search for FPL (requires one if going to TMA, otherwise RADTAG will suffice), cretae/EST/depart and squawk ASSR
  3. If RADTAG, get aircraft to squawk ASSR, put SIS in label
  4. 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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Amended destination

A
  1. C prompt OFF – consider coord
  2. (If in CTA) Put on heading that directs them towards requested destination
  3. RER and coordinate as necessary, C prompt ON
  4. Issue the clearance (including “resume own nav” if on a heading)
  5. Contact FDC

Remember – if a level change was requested with amended destination, change the PCLs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly