AFAE - IFR Training DRAFT V0.7
AFAE - IFR Training DRAFT V0.7
IFR Training Initial version 03/2022 by Emeric Vernédal. NOT an OFFICIAL document. V0.7
T
General preparation 4 Minimum altitudes 16
GPS planning 5 Holding patterns 17
Official Flight Plan 5
Approach 19
Take-off minima 5
Commencement of the approach 19
Landing minima 6
Generalities
Take-off alternate
En-route alternate
Destination airport
AF 6
6
6
6
Initial approach segment with course reversal
Course reversal with a base turn
Course reversal with a procedure turn
Course reversal with a racetrack
19
19
20
20
Final approach segment - Generalities 21
Destination alternate 7
Failures during the approach 21
Basis of flying IFR 7 Direct approaches 22
Generalities 7 Definition 22
Corrections to maintain a track/radial 8 Non Precision Approaches (2D) 22
Interception of a new radial < 20° 8 2D with Distance information (CDFA) 22
R
Variation 8 2D with fix as FAF (CDFA) 22
Interception with 30° method 8 2D not in CDFA 23
Interception under 90° 8 Precision Approaches & APV (3D) 24
DME Arc 9 Indirect approaches 24
Turn anticipations 9 Circling 25
Cockpit preparation & radio means 10 VPT 25
D
T
secondary area of holding pattern,...
> Non-Commercial operation of Other than
○ “Arithmetic” (sum of all maximum
complex motor-powered aircraft
deviations expected). Ex: primary areas of
● MPA: Motor-Powered Aircraft
holding pattern.
● LVTO: TO with RVR 75-400 m
○ “Quadratic sum” (sum of some of the
recommended in NCO
AF
● CDFA: Continuous Descent Final Approach
> If possible: mandatory in CAT,
T
radar vectoring. ● Select SID (not mandatory except if
○ Particularly important in final approach specified), route (airways or DCT if < 50 NM),
segment of 2D APP STAR and most suitable alternate(s)
○ Particularly important when T° < ISA (we (operations, weather conditions, PAX, …)
are lower than indicated) ● Consider several routes according to:
AF
○ Value of correction (in ft)
4 x Δ T° x Alt (in 1000 ft)
Δ T°: difference between ISA and current
○ Distance
○ Minimum altitude (O2, engine restart, …)
○ AWY restrictions, special airspaces,
○ Required navigation capability (RNAV)
○ …
● Study of communication failure during
departure, cruise, arrival (check charts and
general procedure)
● Prepare following documents with know
information:
R
○ Flight log
○ Fuel planning (see below)
○ Mass & balance
○ TO / LDG data card
Altitude
D
T
(“Impair” <-> “Italie”) ● Extra fuel:
○ Airway: ○ Fuel already in the tanks
Check if AWY available in both directions ○ PIC decision (ex: expect to hold 20 min)
+ altitude (can be different from ● Block fuel: minimum fuel + extra fuel
semicircular rule) ● Safety fuel:
○ In flight: ATC
AF
○ Wind: check WINTEM to identify at which
level wind will be more favourable
○ NCO: same rule as CAT except if PIC can altitude, fuel consumption between WPTs
determine if supplemental O2 is needed ● File official FPL (see below)
(before flight: analysis of flight and PAX, in ● Update following documents:
flight: monitoring & detection of symptoms) ○ Flight log with WPTs, distance, track, time
● Calculate POD/TOD according to expected without wind, safety altitude.
cruise level and expected QNH (see “Arrival - > WPTs: DEP, end of SID, turning points
Preparation” for calculation details) or compulsory reporting points, entry of
STAR, expected IAF, DEST, ALT(+route if
necessary)
○ Fuel planning (effect of wind, actual fuel in
tanks, effect of Wx conditions?, …)
○ Mass & balance: actual mass of fuel in the
tanks
○ TO / LDG data card: actual TOW (and
associated speeds / performances)
GPS planning ○ Number of POBs, Name of the PIC, phone
● If planning to use GPS for navigation and/or number
approach: ○ Route (SID/STAR, AWY, DCT)
○ Check GPS Notams ● Activation of the FPL in following timeframe
○ Compute RAIM at ETA (not legally Standard: ± 15 min
required if using SBAS). Via Augur or in With slot: - 5 to + 10 min
the plane ● Cancellation: if the mission is cancelled, do
○ Check navigation database in the plane not forget to cancel the FPL.
● If planning to use an RNP approach: ● Tip: before submitting the flight plan,
> At least one conventional approach must double-check everything with a “new eye”
be available at destination airport or (and/or with your binôme)
destination alternate
● Waypoints: not possible to add a WPT in the
Take-off minima
database or change a WPT from flyover to
T
flyby. Only use WPTs contained in ● Check ATIS information by tel if available
procedures ● Other than NCO: no take-off if Wx at
● Flight plan: provide RNP capability in “Other departure AD is not above landing minima
information” after “PBN /” (see details below) (except if a suitable TO alternate is available)
● RNP APCH ≄ RNP AR ● RVR / VIS
AF
(Authorization Required)
● Types of APP and associated minima
○ LPV -> APV SBAS
○ When no RVR and no VIS (or VIS <
minima): The PIC can begin TO if he
estimates RVR/VIS is above minima.
○ When no RVR or no VIS: the PIC
○ LNAV/VNAV -> APV BaroVNAV
○ LNAV -> NPA (perform CDFA) double-check if he estimates RVR/VIS is
● SDF: if a step down fix is published (need to above minima.
check distance before descending below a ● Required RVR/VIS (not LVTO):
given altitude) > only used for LNAV minima ○ CAT or NCC:
If multi-engine aircraft able to stop or
Official Flight Plan continue TO (with failure of critical engine)
R
● At least 60 min before departure, or if in flight to 1500 ft AAL while maintaining obstacle
10 min before entry in area / crossing AWY clearance, RVR/VIS ≥
● For flexibility & convenience: use Autorouter ■ Day: 500 m
● Aircraft: create / import your aircraft. ■ Day + lights (edge or centerline): 400 m
○ Equipment & capabilities: BDGLORY S ■ Night + lights
B (LPV), D (DME), G (GNSS), L (ILS), O (edge + end or centerline + end): 400 m
D
T
*: or pursuit in flight with change of FPL
● Mostly used for fuel planning optimization on
○ In-flight:
long flights in CAT
CAT & NCO: no pursuit of the flight if
○ Distance requirements: in a circle with
available Wx information for destination or
■ center located at 25% of total flight from
destination ALTN < minima.
● TAF interpretation
○ BECMG … FROM … TO …
AF
■ Deterioration > consider FROM
■ Improvement > consider TO
destination (or 20% + 50 NM) > biggest
■ radius of 20 % of total flight
○ Minima: same as destination alternate
● ETOPS en-route alternate (SPA):
Wx at ETA to ETA + 1h ≥
○ “TEMPO” or “PROB30/40”
○ PA: minima +200 ft (DA) +800 m (RVR)
■ Deterioration - Persistent: consider
○ NPA: minima +400 ft (DA) +1500 m (RVR)
■ Deterioration - Transient: may disregard
■ Improvement: disregard in all cases
○ “PROB30/40 TEMPO” Destination airport
■ Deterioration: may disregard
● Check at least one conventional approach at
R
■ Improvement: disregard in all cases
destination airport or destination alternate.
● Single pilot operations - RVR for landing
● CAT - Destination airport
○ For single-pilot operations, the minimum
○ Wx at ETA ± 1h ≥ minima
required RVR for an approach can be
● NCO - Destination airport:
limited if certain conditions are not met.
Wx at ETA ≥ minima
○ If no centerline and/or touchdown lights:
● Isolated airport:
D
T
VIS ≥ 5 km ● Fly with minimum input on the stick (except
○ 2 destinations alternates if: to counteract turbulences), small corrections,
■ No Wx information at destination elbow blocked on armrest if possible
■ Wx at ETA ± 1h at destination < minima ● Trust your instruments
● NCO - Destination alternate requirements
○ 0 if:
AF
○ 1 destination alternate normally required
■ Wx at ETA ± 1h ≥ VMC
● IMC and icing conditions: alternate air
● If any doubt (position, attitude, …): confirm
with other instruments. Never leave doubt
● Do not follow GPS instructions blindly:
or always keep situation awareness and check
■ Isolated AD & Instrument approach is if next waypoint / current track is coherent
prescribed & Wx at ETA ± 2h: ● Wind above boundary layer (2-3000 ft)
Cloud base ≥ 1000 ft above minima compared to wind at surface
VIS ≥ 5,5 km or ≥ 4 km above minima Mnemonics: left hand, thumb up
● Minima - Destination alternate ○ Wind direction: +30°
○ CAT - Destination alternate minima ○ Strength: x2
R
■ Depending on desired APP type: ● TAS = IAS + 1% per 600 ft of altitude
APV LPV > NPA or CAT I * ± 1% per 5° ∆ISA (+ if warmer, -
CAT II & III > CAT I colder)
CAT I > NPA ● Basic factor (BF)
NPA > NPA +200ft +1000m ○ Gives time to fly 1 NM
Circling > Circling ○ BF = 60 / GS (min)
D
T
by 10°
○ Tips when wind not available
○ etc
■ Visualise the wind direction on HSI
○ Perform last turn to align on desired track
■ Calculate the drift with numbers above
● Tips:
or by visualising on the HSI
○ visualise: current position, desired track
(consider HSI radius = max drift, report
AF
the wind vector on the horizontal axis
and “read” the drift value)
and direction of first turn + direction of
following turns (opposite)
○ Calculate the anticipation of the last turn
depending on the interception angle
Corrections to maintain a track/radial (see “Turn anticipation below”)
● Conventional navaids
○ < 5° difference: alter current track by 5° Interception with 30° method
○ > 5° difference: alter current track by 10°
● When inbound a fix: ± 30° from current radial
● GPS in ENR mode
● When outbound fix: ± 30° from desired radial
○ 1 dot: alter current track by 10°
R
○ 2 dots: alter current track by 20°
Interception under 90°
Interception of a new radial < 20° ● When difference of radials 30-60°
● Alter track to intercept the desired radial
● When the desired track is inbound
under 90°
○ If < 3 min: converge by 2 x ∆ (max 30°)
D
● Anticipation : GS / 3D
○ If > 3 min: converge by 3 x ∆ (max 45°)
● Tip: when the desired CRS is set, it is easy to
● When the desired track is outbound
visualise the 90° interception track: facing the
Same except we apply alteration to the
desired radial. line with o o o o
● Tips:
○ To know the time: check FPL or calculate
Distance x Basic factor or 1 min = X NM).
○ Possible to use the 45° marks on EHSI to
easily visualise a 45° angle
DME Arc ● Corrections in a DME Arc
○ If too close to the station: maintain the
● Aim: maintain a given distance from a station
current track.
in order to intercept a given track
○ If too far from the station & station behind:
● General idea: instead of flying an arc of a
alter track by “closing” by 10° and wait for
circle, a DME arc consists of several “facets”
effect.
(more practical).
○ Wind correction: work with the track and
● Safety / margins :
use corrections above.
○ Protection guaranteed with ± 1 NM from
○ If strong wind, possible to anticipate a
published DME distance.
WCA. When inbound/outbound the navaid
○ Operational margin: 0,5 NM
used for the DME Arc, check HWD/TWD
○ Gap to work with 0,2 NM
component: it will become a XWD
● Method with VOR-DME
component on the first “facet” of the DME
○ visualise: the current position, the desired
Arc (it is therefore possible to “adjust” the
T
track and the directions of first turn +
neutral position of the needle accordingly).
following turns + last turn
Example: work with +10/0° or 0°/-10°
○ Calculate the lead distance anticipation :
instead of +5°/-5°
GS/200 + 0,2 NM margin. Tells when to
start the first turn (+ DME Arc distance). Turn anticipations
AF
Tip: at 150 kts approx. 1 NM.
○ Confirm the direction of the first turn
○ Calculate the first track to intercept the
next radial ± 10° under 90°.
● Lead angle: difference of radial at which the
turn should be initiated
○ Interception under 30° : GS / 9D
○ Interception under 60° : GS / 6D (or 10 / T)
Tip: the first track is 80° from the current
○ Interception under 90° : GS / 3D (or 20 / T)
track if inbound, 100° if outbound.
● Possible to adjust anticipation according to
○ When approaching the lead distance:
the wind
set HDG bug and turn.
○ Tailwind: +50%
○ When established on the track, set the
○ Headwind: -50%
CRS on the exit course of the DME Arc
○ For 90°: tailwind 30/T, headwind 10/T
○ When the needle of the RMI is at 0°:
R
● Tips:
check distance and, if needed apply
○ Read the angle on CDI (check value of 1
correction
dot depending on navaid)
○ When needle at -5° (+5/-5) method:
or by checking the needle (less precise
“close” HDG by 10°… etc
but more anticipation)
○ Perform last turn to align on desired track
○ Round up all the values (GS, Distance) to
(anticip. GS / 3D as we intercept under
D
T
■ Continue flight as per FPL (filed or ● DME
amended by ATC) except if VMC & PIC ○ Range: optical
considers better alternative ○ Accuracy: ± 0,2 NM
■ Maintain last assigned FL / speed ○ Tips:
… for 20 min (7 min if under radar) after > When reading a DME distance, always
AF
reaching FL / setting 7600 / next CRP
… then as per filed FPL
■ Arrive at IAF at cruising altitude and
hold ● ILS
confirm correct frequency
> Possible to keep a DME distance even if
its frequency is not active (“Hold” mode)
T
● Use of CDI to work with ADF:
■ > 1 dot: HDG mode to reach ≤ 1 dot,
Set “fake” NAV frequency: 110.0. It helps to
(NAV mode in standbye)
materialize a CRS.
■ Tips:
● CDI full-scale deviation (2 dots)
> Caution when changing CDI in NAV
○ VOR: 10°
mode! Switch to HDG mode before.
○ ILS LOC: 2,5°
ILS GS: 0,7°
AF
○ GPS (G1000) - Sensibility & RAIM alert
■ ENR: ± 2 NM (± 5 NM if no SBAS)
● Descent:
> In SIMULATOR only: if GPS is current
NAV mode, it will disconnect and switch
to ROL mode after a RAIM check
T
CDI, bearing pointers, DME distance
○ Select COM frequencies
○ Select QNH
○ Select “Minima” Take-off
IFR Tosa = AD elev + 1500 ft
● DA42 standard IFR Take-off
● Departure briefing:
AF
○ Set Altitude bug to MSA
○ Set HDG bug to runway QFU
T
■ Pitch +10°
engine failure height
■ Speed: 85 kts
● Name of the SID: last point of the trajectory
(max AoB 10° as 1,2 Vs)
● Can be either conventional or RNAV.
○ At IFR TOSA (AD elev + 1500 ft)
If RNAV: possible to do with GPS overlay.
■ Pitch +7°
■ Speed: 100 kts
■ Pump OFF
■ FPL page on MFD
○ After TO checklist
AF ● Contains published tracks, radial
interception, altitude constraints, support
navaids, …
● Track can be described in two parts:
“Initial climb” + rest of the routeing
Tip: “altimeter set & compared” > If main
altimeter at 1013: calculate expected Omnidirectional departure
difference (QNH-1013 x 30 ft) and check
● Type A: specified route until specified altitude
○ Passing 3000 ft or contact with APP:
Type B: specified route to a fix
landing lights OFF.
● Check “GEN” section and determine
○ When at cruise altitude and speed
conditions, altitude/position of the first turn,
R
approaching 120 kts:
…
■ Cruise power (DA42 70%, SR20 75%)
● “Multidirectional”: when a departure area is
■ Compare altimeters
prohibited
■ Cruise checklist
● Minimum climb path 3,3% except if otherwise
○ ETA next WPT
specified
D
IFR navigation ● At each WPT: TRAIRE
○ Top: reset Timer
Generalities ○ Route: take new track and confirm
○ Altitude: change / confirm altitude
● Determine & brief main mean of navigation:
○ Index: time at WPT, next estimate + Fuel
GPS or Conventional
○ Radio: prepare next radio / navaid freq
● GPS (magenta)
○ Engine: check engine
○ If CDI in GPS and AP in NAV mode, the
● When given a “direct”, update the flight log:
aircraft will automatically follow the track
cross-out the “skipped” WPTs, updated info
loaded in the FPL & anticipate the turns.
in the “direct to” WPT
● Conventional (green)
● When in icing conditions: regular “ice check”
○ If CDI in VOR mode (+ CRS set) and AP
● On a regular basis during the flight or if any
in NAV mode, the aircraft will follow the
change (new level, direct routing, change of
radial set in the CRS (ROL if loss of
procedure): update ETA, playtime, POD, …
signal).
T
Track changes will need to be anticipated
by the pilot. ATC
● Fly-by technique
● Identify enroute expected frequencies/areas
○ Anticipate turn without passing overheads
● When ATC requests “report reaching”
turning point
○ Beginning of turn:
AF
■ VOR: entering cone of confusion
■ Intersection: GS/200
○ Altitude: when within ± 1000 ft before
○ WPT: when within 2 minutes before
● When “radar vectored” or “direct to a WPT
not in the FPL”, ATC becomes also
■ RNAV: when “turn now”
responsible for the collision avoidance with
○ If flying conventional & under AP with
the ground BUT check if > safety altitude or
■ Switch from NAV to HDG mode
radar altitude
■ Prepare navaid + CRS used for next
● 2 minutes before TOD, inform ATC:
segment
“Ready to descend”
■ Perform the turn towards new segment
■ Switch back to NAV mode. If too far
R
from the desired track, use HDG mode In-flight fuel management.
to capture it
● Fly-over technique ● In-flight fuel checks to compare, check and
○ When mandatory to fly overheads a calculate expected fuel at destination
waypoint ● Expected fuel at destination:
○ Wait for the needle to point backwards ○ Normally > ALT + FR
D
T
Max TWD: 10 kts
○ Omnidirectional:
Dry Grass: +20% of ground roll
■ No published route
Wet Grass: +60% of ground roll
■ Safety altitude: MSA
Upslope: -9% per 1°
■ Begins 25 NM from IAF
Downslope: +27% per 1°
Preparation
AF
● Obtain arrival information (ATIS, radio)
○ 15 minutes before POD
■ SR20
HWD: -10% per 14 kt of HWD
TWD: +10% per 3 kt of TWD
Max TWD: 10 kts
○ Request to leave APP freq. a few minutes
Wet RWY: +15%
○ Take arrival/Wx information (DEST +
Dry Grass 5 cm: +10% of ground roll
ALTN). If ATC/AFIS: say ETA at IAF.
(5-10 cm: +15%, >10 cm: +25%)
○ When back on APP, if ATIS confirm letter
Wet or soft Grass: +10% of ground roll
and say intentions (expected APP, full stop
Downslope: +9% per 1°
or not, …)
○ Braking coefficient according to RWY
○ Brief: AD usable, conditions
R
condition
○ Set standby altimeter to QNH at DEST
■ 6: standard (RWY dry)
● Descent calculation
■ 5: good
○ Aim: calculate the descent according to
■ 4: medium to good
altitude constraints + no need to descent
■ 3: medium
too early
■ 2: poor to medium
○ Standard 3° or 2°
D
■ 1: poor
○ POD = ΔAltitude (hundreds) / slope (°)
■ 0: nil
Tip: to calculate easily ΔAltitude, use
○ Effect on landing minima of temporarily
standby altimeter set with QNH at DEST
failed or downgraded ground equipment
○ ROD:
■ Mandatory to take into account if
■ 3° slope: GS/2 x 10.
reported before passing 1000 ft AGL
Tips:
(if after: at PIC’s discretion)
> Almost always possible with SR20
■ Effects (without LVO approval):
> Max GS: 160 kts (to be < 800 ft/min)
(if no effect: not reported in table below)
■ 2° slope: GS/3 x 10
■ Consider following table:
Tip: (If GS = 180 kts, ROD = 600 ft/min)
■ GS: consider increase of speed during
descent, wind, expected turbulences
(< VNO: 151 kt DA42, 163 kt SR20)
○ TOD = Δ Altitude / desired ROD
○ 2° > 200 ft per NM | 3° > 300 ft per NM
Equipment CAT I APV & NPA Arrival briefing & actions
Outer Marker Must be replaced Only if OM is FAF
● Arrival briefing
by a height check of NPA and no ○ Destination AD:
at 1000 ft other way to ■ Accessible? If no: new plan of actions
identify it: APP
not allowed ■ Current conditions (RWY in use and
state, wind, ceiling,...)
Middle Marker - No effect except if ○ Current position
MM is FAF
○ Type of descent and POD
Approach Lights Minima of NALS ○ Name of requested APP & Runway
(No Approach Lighting System)
○ Version of the file
APP Lights Minima of BALS ○ Means used for the approach
except last 210 m (Basic ALS) ○ THR / AD elevation
APP Lights Minima of IALS ○ MSA
T
except last 420 m (Intermediate ALS) ○ IAF: name, ETA, trajectory after IAF
○ FAF/P and approach altitude
Edge lights, THR Day: -
lights and RWY Night: APP not allowed ○ Descent slope: standard/non-standard,
end lights announce descent rate according to
expected Ground Speed
Centerline lights
or
Touchdown zone
lights
AF
Min. RVR: 750 m
Except if F/D,
HUDLS or
Autoland: no
effect
No effect ○ Minima
○ Missed Approach procedure and altitude
○ RNP: extraction procedure
○ Radio failure (check “GEN” section)
○ TEM
CAT I: RVR according to DH ○ Questions?
DH FALS IALS BALS NALS
T
○ Max speed: <14000 ft 170 kt for cat A, B.
● Types of entry
230 kt for other cat. Unless specified.
○ Protected area:
■ Primary area: exact dimensions
generally not known (1000/2000 ft
OCH)
AF
■ Buffer area: 5 NM around
● Method - Approaching the fix
○ Reduce speed (Power 45% on DA42, 60%
on SR20)
○ Flexibility between sectors: ± 5°
○ Select inbound CRS
○ Parallel entry
(if fix is a NDB: use “fake” VOR 110.0)
○ Teardrop/offset entry
○ Set “Holding at waypoint” on FPL.
○ Direct entry.
If option not available: “Direct to” and
○ Tip: to identify / confirm entry type:
initially select “Hold” instead of “Activate”
1. Take a track towards the fix
○ Prepare timer
R
2. When track established, visualise the
○ Tip: Visualise HP on EHSI (the plane
following diagrams
symbol being the fix).
3. Check in which area the CRS pointer’s
head is (in grey below) and “read” the
entry method.
D
T
OR direct to fix. pointer at 90°): start timer
○ Align on the inbound track ○ Correct for wind effect
○ After time / on limiting radial:
● Method - Teadrop/offset entry Turn, correct wind effect, confirm leading
radial, continue turn
AF ○ Align on inbound track
○ Repeat
● Wind corrections
○ In holding pattern but also during entries
○ XWD: with diamond / TRK
○ When passing over the fix, follow the ○ HWD/TWD on outbound leg of HP
limiting radial (MUP: 30° not 40/T ?XXX) + outbound leg of parallel/teardrop entries
○ Start timer when wings level ■ Time correction in sec:
○ Correct for wind effect HWD/TWD kts x 1,5 (x time in min)
R
○ Turn, correct wind effect, continue turn ■ Add if HWD, subtract if TWD
○ Align on the inbound track ○ HWD/TWD in turns
■ In turns of HP + turns of parallel /
● Method - Direct entry teardrop entries
○ Enter directly into the hold (see holding ■ Stop turn after 90° and analyse wind
method below). ■ If TWD: nothing to do, continue turn
D
T
○ Conversion coefficients: RVR x coeff
■ HI APP lights: x1,5 by day x2 by night
■ Other lights: x1 by day x1,5 by night
■ No lights: x1 by day n/a by night ● Defined by:
○ A fix
AF
○ Start of APP: RVR/VIS can be disregarded
○ 1000 ft windows*: RVR/VIS > minima
(* or when beginning the final app
segment if MDA > 1000 ft, or at OM)
○ An outbound leg + an inbound leg
○ A time, a distance, a radial or another fix
to determine the end of the outbound leg
○ Below 1000 ft: if RVR/VIS deteriorates ● Method:
below minima, possible to continue APP ○ Determine how to enter via the protected
down to minima area: ± 30° of the outbound track
● Direct entry requirements + area to include the extension of the
○ Conventional: inbound track.
■ Course reversal with procedure/base A holding pattern can exist around the fix
turn: arrival track < 30° of outbound leg to facilitate the entry
R
(ext. to include opposite of inbound leg) ○ Select outbound CRS
■ Radar vectoring to FAF/P possible ○ When passing the fix, start timer and take
○ RNP: outbound track
■ Arrival track ± 110° of axis IAF > IF ○ NPA only: on outbound track > flaps +
■ Radar vectoring after IAF: gear
Possible to accept radar vectoring ○ At the end of the outbound track: select
D
T
○ Via holding pattern over the same fix
Descend at MHA.
○ Determine how to enter via the protected ○ Omnidirectional entry possible (same
area: ± 30° of the inbound leg methods as holding pattern) only if:
■ Altitude of racetrack and MHA are the
T
> Flaps 50/APP when speed allows contingency plan, … Check with QRH
■ Tips: ○ Decision: plan of actions
> Remain below Vno if turbulences ○ Inform: crew, PAX, ATC, …
> Counteract effects of configuration ● RNP:
changes (slope, attitude, …) ○ Check GPS mode before FAP:
● Stabilisation windows
○ Altitude:
■ IFR IMC: 1000 ft
■ IFR VMC: 500 ft
AF > LPV amber: prepare LNAV minima
(If becomes LNAV: nothing to do. If
becomes LNAV/VNAV update minima)
> Remaining on TERM: abort approach
■ VFR: 300 ft ○ GPS LOI or downgrade: extraction
■ NPA, Circling, VPT: always 1000 ft procedure (to brief). Check Fred XXX
■ NPA without distance information: no > If long before FAF/P of a conventional
Stabilisation window. APP with same axis: ask ATC and switch
○ Callouts at Stabilisation window > If after FAF/P, VMC: continue visual
“Stabilised”: vertical / lateral / speed > If after FAF/P, IMC: climb RWY axis to
“Configured”: flaps, landing gear
R
MSA and request radar vectoring to IAF of
“Landing checklist complete” a conventional APP.
> “Continue” or “Go Around” ○ Phraseology: inform ATC when failure:
● Corrections “Unable RNP approach due to GPS LOI /
○ Above Stabilisation window: loss of RAIM / …”
■ HDG: ± 4° ● ILS:
■ Pitch: ± 1° ⇔ ± 100 ft/min
D
T
if FAF* (if not, see “NPA not in CDFA”) ○ 200 ft below: “dong” of altitude bug
● CDFA - Set missed approach altitude
○ Continuous Descent Final Approach - Landing checklist (by memory)
○ No level flight segments at MDAs after ○ 0,5 NM before each NM: check on the
beginning the final approach descent chart at which altitude we should be and
○ Conditions:
a navaid)
AF
■ Defined FAF (by distance or overhead
T
procedure turn and threshold > If no (or too late): continue until MAPt
○ Time of descent = same as outbound leg and execute missed approach
○ Calculate ROD = altitude to lose / time of
descent
The aim is to intercept the MDA with
timing
● Method:
AF
enough margin before MAPT /end of
○ During turn
■ Rate one turn
■ Speed reduction (power setting 30%
DA42, 50% SR20) to get 100 kt
■ Flaps APP/50
■ Calculate leading radial to finish the
turn
○ When exiting the turn (wings level)
- Confirm if in window (5° VOR, 10° NDB)
- Gear down
- Reset and start timer
- Begin descent with calculated ROD
○ 200 ft below: “dong” of altitude bug
- Set missed approach altitude
- Landing checklist (by memory)
Precision Approaches & APV (3D) Indirect approaches
● Definition: lateral + vertical guidance ● Definition: visual phase of an instrument
Can be: ILS, MLS, PAR, GLS, APV SBAS approach to bring an aircraft into position for
(LPV), APV BaroVnav (LNAV/VNAV) landing on a runway which is not suitably
● Determine ROD based on expected Ground located for a straight-in approach.
speed on final. ● Final track compared to RWY axis
● Interception of final approach axis under 45° ○ Cat A,B: >30° | Cat C,D,E: >15°
(ILS: intercept LOC before glide) ○ At 1 NM from THR: > 150 m lateral diff.
● Lateral & vertical maximum deviations ● Maintain runway environment in sight
○ ILS: angular only ● Caution: Ground speed during the instrument
■ Localizer: ± 2,5° approach procedure is usually higher than
■ Glideslope: ± 0,7° normal due to tailwind component (important
○ LPV: mix of linear and angular when determining the rate of descent).
■ Axis: ≈ ± 2° (from 2 NM before FAP)
T
● Visibility:
■ Glideslope: initially ± 350 ft ○ Conversion of VIS in RVR: not possible
then ± ¼ of the nominal slope (so 0,75° ○ If VIS given by sector: use lowest VIS
for a standard 3° slope)
then ± 50 ft when approaching ground
■ Consequence: as the glide deviation
AF
becomes linear at the end of an LPV
approach, it is usually more stable than
an ILS.
Circling
● Circling or “Visual manoeuvering”
● Free movement inside a protected area
● Method: depending on aircraft category.
○ Stabilise in level flight at approach altitude ● Visual requirements: runway or surroundings
(power 45% DA42, 60% SR20) ● Protected area
○ When glide diamond moves: “Glide alive” ○ Considering: 20° bank angle & maximum
○ Glide at 2 dots: 25 kt of wind.
- Speed reduction (power setting 30% ○ Area: radius of 2,4 NM (cat A) centred on
DA42, 50% SR20) > 100 kt each threshold (joined by straight lines)
R
- Check Pumps ON (B: 3,1 NM | C: 4,5 NM | D: 5,5 NM |
- Check LAND light ON E: 7,1 NM)
○ Glide at 1 dots: ○ Lowest OCH: 400 ft (cat A)
Flaps APP/50 (B: 500 ft | C: 600 ft | D: 700 ft | E: 800 ft)
○ GLide at 0,5 dot / 0,1 NM before FAP: ● Circling layout: depends on configuration
Gear down
D
T
○ ATC: standard method or follow (B: 500 ft | C: 600 ft | D: 700 ft | E: 800 ft)
instructions ● Minima: use minima published on VPT chart
● Method: (Tip: not necessarily the same as “circling”)
○ Perform published instrument approach ● Tracks may depend on aircraft category
down to circling minima (or higher if ● If dead reckoning (track & distance on chart):
AF
VMC, for example circuit pattern altitude)
○ Stabilise in level flight and target 100 kt
(1,45 Vs | Power 70% initially then less)
○ When visual references + certain to be in
calculate (before flight / APP), the associated
time for each leg (with expected GS)
● Arrival on aerodrome:
○ With AFIS (& reserved for AC with radio):
the protected volume, at the latest at IFR has priority over VFR traffic
MAPt: ○ No AFIS: no priority, same as circling
> Open track by 45° (when using opposite ○ ATC: standard method or follow
RWY approach) instructions
> Start timer ● Method: see “circling” method (above) and
○ After 30-60 seconds, join downwind leg adapt according to the published tracks.
R
○ Length of downwind leg defined by timing: ● If loss of visual reference during circling:
■ Start timing when passing RWY THR Follow MAP published with the VPT
■ 6” / 100 ft of height (+1” per 1 kt of or climb towards AD (best climb rate) & join
TWD) the published missed approach procedure
○ Turn in base, then final (use PAPI if
available) and land
D
T
○ (Flaps Full > App or 100 > 50) ● Wind limitations:
Speed check: DA42 >82kt, SR20 >80 kt ○ SR20
○ (Gear up) ■ Max demonstrated Xwind: 20 kts
○ Flaps UP ■ Max tailwind: 10 kts
Speed check: DA42 >85kt, SR20 >83 kt (+10% of LDG/TO distance / 2 kts)
○ Radio com
○ CAPS altitude
AF
○ IFR Tosa and associated actions
○ When at the end of the MAP procedure,
○ DA42
■ Max demonstrated Xwind:
Flaps UP: 25 kts
Flaps APP: 20 kts
set a new APP in FPL Icing conditions: 20 kts
● Trajectory: follow published trajectory ■ Max tailwind: 10 kts
○ If turn at a specified point: do not turn (+10% of LDG/TO distance / 3 kts)
before or after
○ If turn at a specified altitude: do not turn
below or above
● During the procedure:
R
○ Use AP if available (high workload)
○ Speed: usually holding speed / power
○ New plan of actions
○ Communicate: ATC, PAX
○ New cockpit preparation if needed
○ Adapted briefing
D
● Tips:
○ Be mentally prepared for executing the
missed approach procedure (long term
preparation on the ground + short term
preparation during briefing)
○ When briefing, visualise and memorise the
MAP procedure.
○ On final, keep in mind the first track,
altitude constraint and direction of first
turn.
○ Communication: only when AC configured
& stable, and correct trajectory established