Presentation on theme: "Instrument Flight Rules (IFR) Planning for FS XXI"— Presentation transcript:
1 Instrument Flight Rules (IFR) Planning for FS XXI E Co Aviation Regiment Lowe Army AirfieldCrusaders
2 PurposeTo provide the student pilot with an informative briefing regarding the methods, techniques, and procedures utilized in planning instrument flights.
3 Administrative Considerations Safety Requirements: None.Risk Assessment Level: Low.Environmental Considerations: None.Evaluation: Check on learning questions as required.
4 IFR Flight Planning Topics Weather BriefingNotices to Airmen (NOTAM)Location IdentifiersDeparture ProceduresEn Route ProceduresArrival ProceduresFlight Plan PreparationFlight Plan Activation
5 References AR 95-1, Flight Regulations FM 1-230, Meteorology for Army AviatorsFM , Instrument Flight for Army AviatorsFAA Joint Order H, Location IdentifiersFAA Order , Air Traffic ControlFAA Instrument Flying HandbookFAA Instrument Procedures HandbookFAA Aeronautical Information Manual (AIM)Department of Defense (DoD) Flight Information Publications (FLIP)Visual Flight Rules (VFR) SectionalEnroute Low Altitude (ELA) ChartInstrument Approach ProceduresIFR SupplementFlight Information Handbook (FIH)General Planning (GP)Area Planning (AP)Airport Facility Directory (AFD)TM Operator’s Manual UH-60A/L/EH-60A Helicopter
6 Requirement to Operate IFR (1) All Army aircraft that are instrumented for IFR flight and are flown by an instrument rated pilot will operate on IFR flight plans except when –(a) Flight is primarily for VFR training.(b) Time will not permit mission completion under IFR.(c) Mission can only be accomplished under VFR.(d) Excessive air traffic control (ATC) departure, en route, or terminal area delays are encountered.(e) Hazardous weather conditions must be avoided.(f) Aircraft is being flown single pilot.AR 95-1, Para 5-2 d (1), page 32
7 Task 1006 Task, Condition, Standards Plan an instrument flight rules flightCONDITIONS: Before instrument flight rules flight in an H-60 helicopter, given access to weather information, notices to airmen (NOTAMs), flight planning aids, necessary charts, forms, and publications.STANDARDS: Appropriate common standards plus the following additions/modifications:1. Determine whether the aircrew and aircraft are capable of completing the assigned mission.2. Determine whether the flight can be performed under instrument flight rules (IFR) per AR 95-1 and applicable Federal Aviation Regulations (FARs)/host-nation regulations, local regulations, and standard operating procedures (SOPs).3. Determine the departure, en route, and destination procedures.4. Select route(s) and altitudes that avoid hazardous weather conditions, do not exceed aircraft or equipment limitations, and conform to IFR cruising altitudes per Department of Defense flight information publication (DOD FLIP).5. If off airway, determine the course(s) ± 5 degrees.6. Select an approach that is compatible with the weather, approach facilities, and aircraft equipment; determine if an alternate airfield is required.7. Determine distance ±1 nautical mile, true airspeed ±5 knots, ground speed ±5 knots, and estimated time en route (ETE) ±1 minutes for each leg of the flight.8. Determine the fuel required per AR 95-1 and FM , ±100 pounds.9. Complete and file the flight plan per AR 95-1 and the DOD FLIP.10. Perform mission risk assessment per unit SOP.Excerpt of Task 1006 as published in TC 1-237
9 Weather PlanningWeather information for the DD Form will be obtained from a military weather facility.(7) Weather briefing. Local commanders will establish policies specifying when DD Form (Flight Weather Briefing) is required to be filed with DD Form 175 (Military Flight Plan) and the minimum entries required on parts I through V of locally briefed DD forms. Weather information will be obtained from a U.S. Military weather facility. If U.S. Military weather service support is not available, consult DOD/US Government FLIP for guidance. Request for exceptions should be submitted through command channels to the commander USAASA. For all IFR flights and/or cross country flights, the weather forecast will be void 1 hour and 30 minutes from the time the forecast is received provided the aircraft has not departed. Weather forecast may be extended after coordination with a weather facility. The crew should update weather briefing information on stopover flights.AR 95-1, Para 5-2 (7), page 32If a military forecaster is not available, the PC willconsult DoD/US Government FLIP for guidance toobtain the weather forecast.The crew should update weather briefing informationon stopover flights.
10 Weather Planning (Continued) C-2 METEOROLOGICAL INFORMATION1. TELEPHONE WEATHER/NOTAM BRIEFINGS(AFFSA/AFFSA)a. Military pilots departing a location where military weather and NOTAM services are notavailable will obtain required information as follows:(1) Contact the Operational Weather Squadron (OWS) responsible for your area.OWSs are located worldwide to be the primary 24-hour weather-briefing source. Local base/postweather flights may assist transient aircrews if and when higher priority taskings and local missionsupport allow. Contact information is listed on the following pages; or(2) Obtain information from published Command-approved weather sources.(3) Obtain information from the US National Weather Service (http:// aviationweather.gov/)(4) Obtain information from an NWS/FAA-approved source IAW FAAO (http:// fsims.faa.gov).(5) Obtain information from accredited local agencies.(6) Real time NOTAM updates are available at https://notams.jcs.mil.b. When talking to a military forecaster, please provide the following information at least 2hours prior to desired brief time:(1) Name of person calling.(2) Aircraft type and call sign.(3) VFR or IFR and proposed altitude.(4) ETD for departure point and ETA for destination and alternates.(5) Route.(6) Enroute stops, if applicable (in order, with ETAs)FIH, Appendix C-2
11 Weather Planning (Continued) CONUS Air Force Operational Weather Squadrons (OWS) Areas of Responsibility (AOR), FIH, Appendix C-3
12 Weather Planning (Continued) 26 OWS AOR Contact Numbers FIH, Appendix C-7Marine Corps/Navy Areas of Responsibility (AOR) FIH, Appendix C-3
13 Weather Planning (Continued) Note: For explanation of DD Form entries see FM Appendix C.Sample DD Form 175-1
14 Weather Planning (Continued) Example of DD Form 175-1 Weather Briefing 16/114316/123816/234317/000917/004217/083827/ +06/ +03TOIMGMALL AREASSFC - 060TOI - MGMExample of DD Form Weather Briefing
15 Weather Planning (Continued) Example of DD Form 175-1 Weather Briefing 280/05TOI3/4 FG BKN OVC C260/10MGM3 BR SCT BKN CX134.1XPHONE:orRequest PIREP on 134.1– JC CW3 Jones1440Example of DD Form Weather Briefing
17 Flight Information Publications (FLIP) DoD Flight Information Publications (FLIP) contain worldwide aeronautical information required in the planning and execution of VFR and IFR flight.DoD FLIP product groups are aligned with the three flight phases (Planning, Enroute, and Terminal).Note: Downloaded products should be cross checked against traditional paper FLIP.
19 Flight Information Publications (FLIP) (Continued) Flight Information Handbook (FIH)
20 Flight Information Publications (FLIP) (Continued) Enroute and Terminal PublicationsIFR SupplementEnroute Low Altitude ChartInstrument Approach Procedures (IAP)
21 Flight Information Publications (FLIP) (Continued) Enroute and Terminal PublicationsAirport/Facility Directory (A/FD)VFR SupplementNote: The Airport/Facility Directory will replace the VFR supplement at a time TBD.
23 Notices to Airmen (NOTAM) Information considered essential to the safety of flight aswell as supplemental data to other aeronautical publications.NOTAM information for DoD aircrews is obtained using the Defense Internet NOTAM Service https://www.notams.jcs.mil/.NOTAM information may also be https://pilotweb.nas.faa.gov/distribution/home.html should the DINS server be out of service.NOTAMs are separated into four types:Distant (D)Flight Data Center (FDC)PointerMilitaryNote: FAA NOTAM “D” Standardization briefing has removed all reference to “L” NOTAMS effective 28 January 2008.
24 Notices to Airmen (NOTAM) (Continued) "D" NOTAM: Information that requires wide dissemination and pertains to en route navigational aids, civil public use landing areas, seaplane bases, and heliports listed in the Airport Facility Directory (AF/D). FDC NOTAM: NOTAM information that is regulatory in nature and transmitted by the National Flight Data Center (NFDC). FDC NOTAMs contain such information as amendments to published IAPs and other aeronautical charts. They are also used to advertise Temporary Flight Restrictions (TFR) such as natural disasters or large scale public events that may generate congestion of air traffic over a site.
25 Notices to Airmen (NOTAM) (Continued) Pointer NOTAM: Information issued by a flight service station to highlight or point out another NOTAM. Pointer NOTAMs assist users in cross-referencing important information that may not be found under an airport or NAVAID identifier.Military NOTAM: Information pertaining to U.S. Air Force, Army, Marine, and Navy navigational aids/airports that are part the of the NAS.
26 Notices to Airmen (NOTAM) (Continued) NOTAM “D” Standardized Format
27 Notices to Airmen (NOTAM) (Continued) Defense Internet NOTAM Service (DINS) web site
28 Notices to Airmen (NOTAM) (Continued) Note: For IFR flights, use the Flight Path Search engine for NOTAM research to include ARTCC/UIR/FIR NOTAMs.Defense Internet NOTAM System (DINS) web site
29 Notices to Airmen (NOTAM) (Continued) Sample NOTAMS for Tallahassee Regional Airport (KTLH)
30 Notices to Airmen (NOTAM) (Continued) Notices to Airmen Publication (NTAP)
31 Notices to Airmen (NOTAM) (Continued) NTAP is an integral part of the NOTAM system. NTAP is published every four weeks and contains information to reduce congestion on communications circuits.Once published electronically, that information contained is not provided during pilot briefings unless specifically requested by the pilot.All information contained will be carried until the information expires, is canceled, or is published in other publications such as the AF/D.NTAP information can be
32 Notices to Airmen (NOTAM) (Continued) If a proposed flight will terminate at a civil airport, aircrews should obtain/review all Federal Aviation Administration NOTAMs including those contained in the NTAP.Aircrews using DINS will not need to consult FLIP to determine if a location has NOTAM support. DINS will provide a plain language notice, highlighted in red, when a requested location is not in the U.S. NOTAM System.
34 Location IdentifiersPublication listing the 3-4 letter identifier location of airports, navigation aids, fixes, weather stations, and flight service stations. FAA and Canadian locations are provided in latitude and longitude format (degrees, minutes, seconds).Location identifier information can be obtained via the website link:To convert the latitude/longitude format from seconds to tenths of seconds, divide the seconds by An example (WIBIN intersection):N 31° 19 min seconds34.06 ÷ 60 = .567 (.57 in DGNS format)N 31° 19.57
36 Departure ProceduresInstrument departure procedures are preplanned IFR procedures which provide obstruction clearance from the terminal area to the appropriate en route structure. Departure procedures are categorized by two types:TextualGraphicalThere are two types of departure procedures:Obstacle Departure Procedures (ODP)Standard Instrument Departure (SID)If the airport has at least one instrument approach procedure (IAP), and there are no published IFR departure procedures; then an aircraft departing under IFR can ensure obstacle clearance by executing a diverse departure.
37 Departure Procedures (Continued) Graphic Representation of Airplane Diverse Departure Procedure
38 Departure Procedures (Continued) V168400 ftObstacle Identification Slope35 ft AGL1 NMSlope of 304 ft per Nautical Mile (20:1)Graphic Representation of Helicopter Diverse Departure Procedure
39 Departure Procedures (Continued) ATC will not specifically clear an aircraft for a diverse departure; the clearance may simply be cleared as filed.In order to fly a diverse departure, fly runway heading until 400 feet above airfield elevation before executing any turns while maintaining a minimum climb gradient of 200 feet per nautical mile until reaching the required IFR altitude.Diverse departure procedures for heliports are based on flying takeoff heading until 400 feet above airfield elevation while maintaining a minimum climb gradient of 400 feet per nautical mile.
40 Departure Procedures (Continued) Example of Lowe AHP (KLOR) Textual Departure Procedure
41 Departure Procedures (Continued) Example of Cairns Army Airfield (KOZR) Graphical Departure Procedure
42 Departure Procedures (Continued) Climb/Descent Chart (Page 7-151, TM )While planning the departure phase of IFR flight, confirm that the aircraft is capable of completing the departure procedure utilizing the operator’s manual climb/descent charts.
45 Route SelectionDetermine if flight can be completed by means of published routing utilizing en route low altitude charts.Example of Published Routing (V521) as Depicted in En Route Low Altitude (ELA) 21-22
46 Route Selection (Continued) If flight cannot be completed by means of published routing utilizing en route low altitude charts, create user defined direct routing.Utilize VFR Sectional to determine direct routing between NAVAIDS.Determine NAVAID reception along direct routing.Determine minimum en route altitude requirements utilizing mountainous/non-mountainous altitude requirements.Determine routes taking into account NAVAID unusable sectors and reception altitude requirements.
47 Route Selection (Continued) Navigation Aid Reception Class Codes (IFR Supplement)
48 Route Selection (Continued) Example of Wiregrass VOR (RRS) Unusable Sectors in IFR Supplement
49 Route Selection (Continued) Mountainous/Non-Mountainous Areas (Figure 5-6-2, Aeronautical Information Manual)
50 Route Selection (Continued) Highest Elevation Along RouteExample of Direct Routing in Absence of Victor Airway
56 Instrument Approach Minimums Arrival (Continued)Instrument Approach MinimumsH-069°760– Minimum Descent Altitude (MDA)3/4 – Runway Visual Range (RVR)519– Height Above Landing (HAL)600 3/4 – Weather Planning MinimaNote: Decision Altitude (DA) is an ICAO definition (differing from the JCS/NATO definition of Decision Height (DH)) specifying an altitude on a precision approach at which a missed approach must be initiated if the required visual reference to continue the approach has not been established.
57 Arrival (Continued) Additional Approach Information GP Chapter 2, Page 2-2 Explanation of TermsGP Chapter 2, Page 2-2 Explanation of Terms
60 Instrument Approach Considerations Arrival (Continued)Instrument Approach ConsiderationsExample of Inoperative Approach Lighting System (ALS) at Barksdale Air Force Base (KBAD)
61 Alternate Approach Planning Arrival (Continued)Alternate Approach Planninge. Alternate airfield planning. An alternate airfield is required when filing IFR to a destination under any of the following conditions:(1) Radar is required to execute the approach procedure to be flown.(2) The instrument approach navigational aids to be used are unmonitored.(3) The predominant weather at the destination is forecast at ETA through 1 hour after ETA to be less than –(a) Ceiling 400 feet above the weather planning minimum required for the approach to be flown.(b) Visibility 1 mile (or metric equivalent) greater than the planning minimum required for the approach to be flown.(4) An alternate is not required if descent from en route minimum altitude for IFR operation, approach, and landing can be made in VFR conditions.AR 95-1, Para 5-2 (7)(e), page 32
62 Alternate Approach Planning Arrival (Continued)Alternate Approach Planningf. Alternate airfield selection.(1) An alternate may be selected as an alternate when the worst weather condition for that airfield is forecast for ETA through 1 hour after ETA to be equal to or greater than –(a) Ceiling 400 feet above the weather planning minimum required for the approach to be flown and visibility 1 mile (or metric equivalent) greater than the weather planning minimum required for the approach to be flown; or(b) VFR minimums and descent from en route minimum altitude for IFR operation, approach, and landing can be made in VFR conditions.(2) An airfield will not be selected as an alternate except per f(1)(b) above –(a) If the approach procedure to be used at the alternate is shown not authorized (NA) in FLIP.(b) If radar is required for the approach procedure to be used at the alternate.(c) If the instrument approach navigational aids to be used is unmonitored.(d) If a Class B, C, D, or E surface area airspace does not exist or is not in effect at the airport to be used.(e) If the global positioning system (GPS) is required for the approach.AR 95-1, Para 5-2 (7)(f), page 32
63 Arrival (Continued)Descent from Minimum Altitude for IFR Operations in VFR ConditionsMinimum altitude for IFR Operations:Field elevation of Cairns Army Airfield: 301(Min for IFR operations in MSL)(Field elevation)= (Elevation of Cairns AAF at min IFR alt in AGL)(Elevation of Cairns AAF at min IFR alt in AGL)(Basic cloud clearance for VFR)= (Height AGL of cloud requirements)(Cloud Height rounded to nearest 100 ft increment)+ 3 SM (Visibility requirement for VFR conditions)Ceiling/Visibility Requirement:2200 ft Ceilings / 3 SM VisibilityExcerpt of ILS Runway 6 Cairns Army Airfield (KOZR)
64 Arrival (Continued)Copter ApproachesMaximum airspeed is 90 KIAS on any segment of the approach (initial, intermediate, final, missed). Lower airspeeds may be listed on the final and missed approach segments.Reduction of visibility for “copter only” approaches is not authorized as this reduction is already applied.You may hold on copter holding patterns at 100 KIAS. However, once you begin and are established on the inbound portion of the approach, airspeed is limited to 90 KIAS.
65 Excerpt of Copter VOR 069 Lowe AAF (KLOR) Arrival (Continued)Excerpt of Copter VOR 069 Lowe AAF (KLOR)
66 Flight Plan Preparation Parked: G0522 Oct 09R24517H60/UI LOR EDN XNE MGM MARRA MGMI MGM MGM XNE EDN (2+40 OZR 0+18) LORBriefed by: Jones, W. W., CW31ST Request – ILS 28 MGMMGM - S/JK LOR 5 Jun / USAACE / LORSmith, J. K CW E Avn / LORPI Jones, W. C LT D Avn/Ft. RuckerCP Johnson, B. D WO B Avn/Ft. Rucker
67 Flight Plan Preparation Purpose of the flight plan is to communicate the pilot’s desires to Air Traffic Control.General Planning (GP) (Chapter 4) is the reference for completing the DD Form 175 (Military Flight Plan) and DD Form 1801 (International Flight Plan).Depending on unit assignment, other types of flight plans may be required (DD Form 1801, FAA , FAA (Flight Progress Strip)).
68 Flight Plan Preparation (Continued) Stopover Flight PlansEach leg after the initial leg of a stopover flight plan is entered as described in ITEMS (4) through (11).In parenthesis following the last entry of successivelegs, enter the hours of fuel on board (e.g., (2+40)).22 Oct 09I LOR EDN XNE MGM MARRA MGMR23369H60/UParked: W09I MGM MGM XNE EDN (2+40 OZR 0+18) LORTOI /RK LOR 2 Jun / USAACE / LORExample of IFR Flight Plan from Lowe AAF to Montgomery Regional Airport (Dannelly Field) (KMGM) and Return
69 Flight Plan Preparation (Continued) Flight Plans Requiring Alternates FM (Para A-15, page A-4) states that the ETE to the alternate should include time from the:Missed approach procedure to the missed approach holding point to include one circuit in the holding pattern.Missed approach holding point to the alternate including approach and landing time.If an alternate is required for successive legs, enter the airport identifier and the ETE to the alternate in parenthesis with the fuel on board entry (e.g., 2+35 TOI 0+24).
70 Flight Plan Preparation (Continued) Flight Plans Requiring Alternates22 Oct 09I LOR EDN XNE MGM MARRA MGMR23369H60/UParked: W09I MGM MGM XNE EDN (2+40 OZR 0+18) LORTOI /RK LOR 2 Jun / USAACE / LORAlternate Airfield and ETE for 1st Leg of FlightAlternate Airfield and ETE for Subsequent Leg of FlightExample of IFR Flight Plan with Successive Legs Requiring Alternates
71 Flight Plan Preparation (Continued) Flight Plan with Holding Delay Parked: W0922 Oct 09R23369H60/UI LOR EDN XNE BLOOD / D MGM MGMExample of IFR Flight Plan From Lowe AAF to Montgomery Regional Airport (Dannelly Field) (KMGM) with Holding Delay
72 Flight Plan Preparation (Continued) Flight Plan with Terminal Area DelayEnter the delay location airport identifier as the last item in the route of flight.Do not make an entry in the TO block; enter the time required to fly the segment exclusive of planned en route delays in the ETE block.Explain the delay as a remark on the next line in the ROUTE OF FLIGHT block; do not make entries in any other blocks on this linePrecede the delay remark with a circled "R" to indicate that the information to following should be transmitted as a remark.Enter a "D" and the length of the delay, the delay location airport identifier, and the airport of the final destination (e.g., R D 0+15 MAI TLH). Complete items (4) through (11) for the subsequent leg of flight.
73 Flight Plan Preparation (Continued) 22 Oct 09R24623H60/UParked: M10I LOR EDN RRS V MAI MAIR D MAI TLHI MAI MAI SZW GACED TLHExample of IFR Flight Plan From Lowe AAF to Tallahassee Regional Airport with a Terminal Area Delay at Marianna Municipal Airport
74 Flight Plan Preparation (Continued) Estimated Time En Route IFR Flight Plans:The time from takeoff or departure from a Terminal or Special Use Airspace en route delay location to the last fix shown in the route of flight exclusive of planned en route delays.For Army Aircrews, the ETE for IFR flight plans is the elapsed time until over the first point of intended landing.Composite Flight Plans:For each IFR segment, use time planned to fly the segment exclusive of en route delays; for each VFR segment, use time planned to fly the segment including known delays (practice air work, landing, etc.).
75 Flight Plan FilingFlight Plans filed with a military Base Operations are passed to Federal Aviation Administration Flight Service immediately after aircraft departure. Flight Service then notifies the destination base of each aircraft's ETA. Pilots should file their IFR flight plan at least 30 min (45 minutes at LOR and 1 hour in some areas) prior to ETD.Prior to departing civil airports, file the Flight Plan with the nearest Flight Service Station (FSS) via telephonically or by use of aircraft communications if other means are not available using the format contained in FAA FormFlight plans transmitted to FSS telephonically may use the toll-free number 800 WXBRIEF ( ).
76 Flight Plan Filing (Continued) In the event of a delay in excess of 30 minutes from the estimated departure time as filed on the flight plan, an amended or new flight plan should be submitted, whichever is applicable.Flight service stations can provide weather observations and forecasts (terminal and area), but military pilots must obtain their weather brief from military facilities (AR 95-1, Para 5-2 (7), page 32).While communicating with flight service, it is advisable to have available a copy of FAA Form to use as a reference while transmitting flight plan entries.
77 Flight Plan Filing (Continued) Sample FAA Form 7233-1 Flight Plan
78 Flight Plan Activation When departing non-military airfields, the pilot must ensure that the actual departure time is passed to the TIE-IN FSS serving the departure field.The pilot can transmit the departure time through the tower or directly to the tie-in FSS.Flight service will then transmit the departure time to the flight operations facility at the destination, workload permitting.Standard UHF/VHF FSS frequencies are 255.4/122.2 respectively.If the departure time is not passed to the TIE-IN FSS, the aircraft will arrive unannounced at the destination and assistance in flight tracking for emergencies will not be available if required.