The student should gain an understanding of departure and arrival procedures and clearances, as well as a basic ability to read enroute and approach charts.
The lesson will be complete when the student can brief an approach, describe chart elements, and interpret air traffic control clearances with minimal instructor guidance.
Standard Instrument Departure (SID)
Published IFR departure procedure, providing a standard route from the terminal area to the en route system.
- To accept, the DP must be at least written down, and preferably in chart form.
- If not in possession, note “NO DP” in the flight plan.
- ATC might just read the whole thing anyway.
- Exist in vectored and pilot-navigated versions.
Standard Terminal Arrival (STAR)
Established IFR arrival routes for specific, larger airports, designed to simplify clearance delivery.
- Some procedures have mandatory speeds or crossing altitudes published, or information on what to expect.
- Aircraft on a STAR must be cleared to descend; obstacle clearance is the responsibility of ATC.
- Variations include RNAV and Type B, which use GPS or RNAV technology to attain 2nm and 1nm accuracy respectively.
- Different instrument approach types exist, with different arrival procedures, as many have multiple initial approach fixes.
Standard departure and terminal arrival charts
- non-standard take-off minimums (Instrument Flying, 533)
- NOS - listed in front of the packet
- Jepp - per-airport
- SIDs and DPs (536)
- with the approaches for the airport in NOS and Jepp
- list requirements
- illustrate the departure and where it ends (MEAD7.BLD is the Mead Seven departure, BLD transition)
- transition routes lead to and from the enroute system
- chart also includes a textual description for each runway
- symbology is the same as enroute charts
Standard instrument approach procedure charts
NOS and Jeppesen have slightly different formats, but differ only in minor symbology and the depiction of minimums.
- briefing strip
- city (how charts are indexed)
- approach information - nav frequency, course, lengths and altitudes
- approach name
- ICAO identifier and airport name
- requirements, lighting information, missed approach
- radio frequencies
- plan view
- top-down view of the approach
- ADF, DME, or RADAR REQUIRED is printed in the top right corner for some approaches
- effective date (vertical along the side)
- minimum safe altitudes (MSA) listed in bottom right corner
- navaids and frequencies are listed again
- airport plan
- shows airport layout
- FAF to MAP distance and times
- profile view
- missed approach instructions, top corner
- vertical depiction of the approach, from the initial fix on
- shows glideslope intercept and minimum altitudes for the segment
- different minimums for different categories (some overlap)
- list different approach options - straight-in, circling, etc
When briefing for an approach, it’s good to quickly read through the pertinent information, skipping that which is not relevant for our current approach:
- Approach and TDZE (Paine Field ILS to 16R, touchdown elevation 565)
- Nav facility and frequency (IPAE, 109.3 - tuned, identified, course twisted, source selected)
- Comm frequencies (On approach, 16R tower is 132.95 and in standby)
- If major obstacles exist, locate the highest point under the approach and missed (830 MSL tower under the missed approach path)
- Minimums (DH is 781 feet / 200 AGL, RVR greater than 2,400)
- Procedure (We’re northwest and can expect vectors to final at 3,100)
- Runway data - landing distance and lighting available (We’re landing 16R, 9000 feet available, lighting is tower controlled, and once we see the rabbit we can descend to 681.)
- Missed (If missed, climb to 1,300 followed by a climbing right turn to 3,100 direct to RITTS and hold.) Mentioning fuel available for the hold is also a good idea.