Radar Vectors
FAA Order Current Issued Aug 30, 2015 AJF-0 142 pages Copy saved Nov 18, 2026

Order 8240.36N Flight Inspection Report Processing System (FIRPS)

This order provides policy, guidance, and distribution requirements to personnel using the electronic Flight Inspection Report Processing System (FIRPS).

Official source ↗ Open PDF

Text read by OCR from a scanned file (8 of 142 pages). Check the original, as some words may be misread.

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

National Policy

ORDER 8240.36N

Effective Date:

08/30/2015

This order provides policy, guidance, and distribution requirements to personnel using the electronic Flight Inspection Report Processing System (FIRPS).

Federal Aviation Administration (FAA) personnel will protect and archive federal records. Flight inspection reports, data sheets, recordings, electronic media, photographs, and correspondence generated during the flight inspection of navigational aid (NAVAID) facilities and instrument flight procedures are examples of federal records. Reference FAA Order 1350.14, Records Management, for record retention and destruction requirements. In accordance with the Freedom of Information Act, Title 5, United States Code, Section 552, the public may request access to federal records upon written request, unless classified by specific authority.

References to manuals, orders, or technical issuances pertain to the latest published revisions and/or changes. The reader will consider current and active notices and/or technical information when applying this order.

SUBJ: Flight Inspection Report Processing System (FIRPS)

Distribution: Electronic Initiated By: AJW-331

This Page Intentionally Left Blank

.

Table of Contents

8240.36N 08/30/2015

Table of Contents

Chapter 1. Introduction

1. Purpose of this Order … 1 2. Audience … 1 3. Where Can I Find This Order? … 1 4. What This Order Cancels … 1 5. Explanation of Policy Changes … 1 6. Identifying Changes to this Order … 1 7. Definitions … 1

Chapter 2. General Information

1. FIRPS Access … 3 2. FIRPS Description … 3 3. FIRPS Report Life-Cycle … 3 4. DFL & Underlying NAVAIDs … 4 5. Grouping FIRPS Line Items … 4 6. Creating a New FIRPS Report … 4 7. Adding Report Continuation Sheets … 4 8. General Characteristics Form … 4 9. Flight Inspection Results … 4 10. Report Editing … 5 11. Report Amendments … 6 12. Radio Frequency Interference (RFI) Reports … 6 13. Surveillance Inspection Reports … 6 14. Incomplete Inspection … 6 15. ILS/MLS Maintenance Alert Report … 6 16. AIRNAV Data Changes … 6 Security Classification … 6 17. 18. Shipping Recorded Data … 7 19. Lost Recordings Coordination … 8 20. Report Distribution … 8

Chapter 3. Common Report Information

1. Flight Inspection Report Header … 9 a. Ident … 9 b. State & Ctry … 9 c. Inspection Date(s) … 10 d. Location … 10 f. Runway … 10 e. Category … 10 g. Ctrl Number … 10 h. Insp Type … 10

iii

8240.36N 08/30/2015

2. Crew Information … 12 a. PIC, SIC, MS, and ACM … 12 b. A/C NO … 12 c. FIFO … 12 3. Facility Information … 12 4. NOTAMs … 12 5. Remarks … 12 a. IFP Statement … 13 b. SIAP(s) Verified … 13 c. Site Evaluation, NAVAID Commissioning, and Special FI Reports … 14 d. Periodic Requirements … 14 e. SIAP required, but not inspected … 14 f. ARINC Coding Meets Gold Standard … 14 g. Lighting Systems … 14 h. Unsatisfactory Vertical Descent Angle (VDA) … 15 i. Contingency or Natural Disaster Flight Inspection … 15 j. No Electronic Data Required … 15 k. Reference Affiliated Reports … 15 l. Out of Tolerance Conditions … 15 m. Narrative Remarks … 15 n. Data Change Remarks … 16 o. Expanded Service Volume (ESV) … 16 p. 75 MHz Marker Beacons … 16 q. Weather Broadcast Information … 16 r. Critical Area Interference Checks … 17 s. Structure Tolerance (95% Rule) … 17 t. MAGVAR Change Inspection … 17 u. Completion of Previously Incompleted Inspection … 17 v. RFI Checks … 17 w. 1800 RVR … 17 x. Other … 17

Chapter 4. Quality Checklists … 19

Appendix A. FAA Flight Inspection Report Forms

Flight Inspection Report Form List … A-1 Continuation Sheet (FAA Form 8240-1) … A-3 Rho-Theta Systems (FAA Form 8240-2) … A-5 GBAS (FAA Form 8240-4) … A-9 NDB, DF, Lights, Comm (FAA Form 8240-5) … A-11 PAR (FAA Form 8240-6) … A-13 ILS Worksheet (FAA Form 8240-7) … A-17 ILS (FAA Form 8240-8) … A-19

iv

8240.36N 08/30/2015

ILS/MLS Maintenance Alert (FAA Form 8240-11) … A-23 ASR/ ATCRBS (FAA Form 8240-12) … A-25 General Characteristics (FAA Form 8240-13) … A-27 After Accident Continuation Sheet (FAA Form 8240-14) … A-29 MLS (FAA Form 8240-16) … A-31 RNAV (FAA Form 8240-17) … A-35 Data Change Submission (FAA Form 8240-20) … A-37 Obstacle Evaluation (FAA Form 8240-21) … A-39 PRM/FMA (FAA Form 8240-23) … A-41 Appendix B. Rho-Theta Systems … B-1

Appendix C. Ground-Based Augmentation Systesm (GBAS) … C-1

Appendix D. NDB, DF, Lights, and Communications … D-1

Appendix E. Precision Runway Monitor and Final Monitor Aid (PRM/FMA) … E-1

Appendix F. Precision Approach Radar (PAR) … F-1

Appendix G. ILS Worksheet … G-1

Appendix H. Instrument Landing System (ILS) … H-1

Appendix I. ILS/MLS Maintenance Alert … I-1

Appendix J. Surveillance Radar (ASR, ATCRBS) … J-1

Appendix K. General Characteristics … K-1

Appendix L. After Accident Continuation Sheet … L-1

Appendix M. Microwave Landing System (MLS) … M-1

Appendix N. Area Navigation (RNAV) … N-1

Appendix O. Data Change Submission … O-1

Appendix P. Obstacle Evaluation … P-1

Appendix Q. Administrative Information … Q-1

v

8240.36N 08/30/2015

This Page Intentionally Left Blank

vi

Chapter 1. Introduction › 7. Definitions.

8240.36N 08/30/2015

Chapter 1. Introduction

1. Purpose of this Order. This order provides policy, guidance, and distribution requirements for flight inspection reports and records when using the electronic Flight Inspection Report Processing System (FIRPS).

2. Audience. All FAA employees who use FIRPS and its associated forms.

3. Where Can I Find This Order? This order can be found on the Directives Management System (DMS) website at https://employees.faa.gov/tools_resources/orders_notices/.

4. What This Order Cancels. This order cancels FAA Order 8240.36M, and all previous versions.

5. Explanation of Policy Changes. This is a comprehensive revision. Added FIRPS web-based interface guidance to Chapter 2, “General Information”. Chapter 3, renamed “Common Report Information” and relocated report guidance to this chapter; revised report remarks guidance. Updated NOTAM guidance. Added Chapter 4, Quality Checklists. Revised all Appendices; consolidated forms to Appendix A; updated PAR report forms; verbiage updated in Appendices B-Q.

6. Identifying Changes to this Order. Vertical bars in margin are used to identify changes to the original text. Vertical bars are not used in complete rewrites of the basic Order.

7. Definitions. This order contains policy and guidance material. Directive verbs are used.

a. Use MUST when an action is mandatory.

b. Use WILL when it is understood the action is required.

c. Use SHOULD when an action is desirable but not mandatory.

d. Use MAY when an action is permissible.

8240.36N 08/30/2015

This Page Intentionally Left Blank

Chapter 2. General Information › 3. FIRPS Report Life-Cycle.

8240.36N 08/30/2015

Chapter 2. General Information

1. FIRPS Access. Flight Inspection Field Office Mangers will request individual access to the webbased FIRPS interface in accordance with the FIRPS User Manual (select HELP on the main menu to access the FIRPS User Manual). Access FIRPS via the KSN Mission Planning website, or at http://fiog.faa.gov/firps/. Contact the Technical Services Team (405-954-1234) or the ATO Help Desk (405-954-4002) if having trouble accessing FIRPS.

2. FIRPS Description. FIRPS is a web-based system which simplifies the flight inspection reporting, storage, and data retrieval process. The system standardizes reports, expedites the reporting timeline, reduces errors, and tracks changes. FIRPS incorporates up-to-date computer-generated forms and autofills common data from the Flight Operations Management System (FOMS), Daily Flight Log (DFL), and the AIRNAV database.

3. FIRPS Report Life-Cycle. Flight Inspection Reports follow a five-stage life-cycle, each stage with its own status identifiers as shown:

Stage 1: Create Report (Crew)

- Pending (P)

- Rejected (R)

Stage 2: Report Review (Crew)

- PIC Review (PR)

- Tech Review (TR)

Stage 3: Quality Control Review (FIFO)

- Quality Control (QC)

Stage 4: Records Review (FIS Administration)

- Records Review (RR)

- Specialist Review (SR)

- Awaiting Recordings (AR)

- Recordings Sent (RS)

Stage 5: Archive Report (FIS Administration)

Stage 1 begins the date of final inspection, as determined by the DFL. The designated Airspace System Inspection Pilot (normally the PIC) is responsible for on-time report completion. A report is considered incomplete until it reaches the “Awaiting Recordings” status in Stage 4. If a report is rejected, it returns to Stage 1 for crew edit, and is still considered incomplete. Reports not reaching AR status within 60 calendar days of the inspection date are considered “overdue.”

EXCEPTION: The crew must submit after-accident reports no later than 72 hours after the flight inspection. The Flight Inspection Services Technical Services Team will review the report, and ensure it is Archived not later than seven (7) calendar days after the flight inspection. See Appendix L for After Accident reporting requirements.

9. Flight Inspection Results. › c. Non-Applicable Items.

8240.36N 08/30/2015

4. DFL & Underlying NAVAIDs. FIRPS is dependent upon complete and accurate DFL entries. DFL changes may affect FIRPS line items. Therefore, the PIC and MS will ensure reports accurately reflect DFL changes until the report reaches the “Awaiting Recordings” status in Stage 4. When completing the DFL, include an instance of each inspected underlying NAVAID with the appropriate Instrument Flight Procedure (IFP). If multiple instances of the same NAVAID appear on a DFL, select “skip report” on all but the first instance of that NAVAID, unless the crew intends to create separate reports for the NAVAID.

5. Grouping FIRPS Line Items. Group supporting NAVAIDs together in FIRPS (e.g., LOC & GS, or VOR & TACAN). Group only one underlying NAVAID with one or more associated IFP. When more than one NAVAID facility is associated with IFP inspection(s), group IFP(s) with the primary NAVAID, if applicable. Report the additional NAVAIDs separately.

Example 1: Cat I, Cat II, and Cat III ILS Procedures are grouped with the LOC and GS, and reported on an ILS form.

Example 2: Reconfigured GS antenna may be grouped with a LOC periodic inspection of the same ILS facility.

Example 3: VOR ABC and XYZ are underlying NAVAIDS to 3 inspected STAR procedures. ABC seems to be the primary NAVAID. Group ABC with the STARs, then report XYZ separately.

6. Creating a New FIRPS Report. Click on “Select Action” then “Create Report” from the dropdown list. Select the appropriate report form. Verify the correct radio button is highlighted before making the final selection.

7. Adding Report Continuation Sheets. Once the form is created, open the form and select the green “plus” in the upper right corner. Select the appropriate continuation sheet.

8. General Characteristics Form. Report textual departure procedures (ODPs), Wide Area Multilateration (WAM), and Automatic Dependent Surveillance-Broadcast (ADS-B) inspections on the General Characteristics form. Note: Report ADS-B inspections in accordance with FAA Order 8200.45. Use the General Characteristics form when no other form applies.

9. Flight Inspection Results. Report results (measured and/or observed) as required by the flight inspection checklists contained in FAA Order 8200.1. For special inspections, convey in the remarks the flight inspection requirements and final results.

a. Satisfactory/Unsatisfactory. Satisfactory may be designated “SAT" or “S” and Unsatisfactory may be designated "UNSAT" or “U.” Explain unsatisfactory results in the remarks.

b. Asterisk (*). An asterisk identifies items requiring clarification and/or explanation in the remarks. Other symbols may be used to avoid confusion (e.g., #, $, +).

c. Non-Applicable Items. Leave items blank when not applicable to the inspection, unless specified otherwise.

Chapter 2. General Information › 10. Report Editing.

8240.36N 08/30/2015

d. Accuracies. Unless otherwise stated, report numerical data using the following accuracies:

(1) Microamperes - Nearest whole microampere

(2) Altitude - Nearest foot, mean sea level (MSL)

(3) Azimuth - Nearest tenth of a degree

(4) Percent - Nearest tenth of a percent

(5) Mileage - Nearest tenth of a nautical mile (NM)

(6) Angle - Nearest hundredth of a degree

(7) Width - Nearest hundredth of a degree

(8) Coordinates - Degrees, minutes, seconds, and hundredths of a second

(9) Rounding – Round in accordance with FAA Order 8200.1, United States Standard Flight Inspection Manual, paragraph A2.11.b. When averaging multiple measurements, do not apply rounding criteria until the final calculation. Round 1 - 5 DOWN to zero. Round 6 - 9 UP to the next higher value. Exception: If a measurement exceeds the tolerance prior to rounding, do not round into tolerance.

Examples:

Glidepath Course Width: 0.755° = 0.75°

0.756° = 0.76°

PAPI Measurements: Run 1 - 3.23º & 2.74º = Angle 2.985º

Run 2 - 3.25º & 2.70º = Angle 2.975º

Averaged Angle: 2.98º (not 2.97º)

Glidepath Course Width: 0.903° is out of tolerance

10. Report Editing. The crew may edit a report while it is in Stages 1-4. However, when a report reaches “Records Review/Specialist Review” in Stage 4, the crew must contact the Flight Inspection Records Team (405-954-1862) and request the report be returned for editing. The report will appear in the “Rejected” list and return to Stage 1 for crew editing. The report is incomplete until reaching the “Awaiting Recordings” status in Stage 4.

17. Security Classification. › b. Classification Markings.

8240.36N 08/30/2015

11. Report Amendments. Reports reaching “Awaiting Recordings” status in Stage 4 are considered “Archived” and can no longer be edited. Therefore, any change(s) will be recorded on an amended report. Search for the archived report in FIRPS and click on “Select Action.” Select “Amend Archived Report” to generate a new worklist item, as identified by the “Push Pin” icon. The report status will become “Pending” (P), and the amendment number will appear at the top of the report form. Explain the reason(s) for the amendment as well as the extent of the changes in the remarks. Amended reports follow the same flow through FIRPS, but will remain on the original timeline. Complete amendments as soon as possible. NOTE: For After Accident (AA) amendments, notify the Flight Inspection Records Team (405-954-1862). The most current AA report will be the final report submitted to the investigating authority.

12. Radio Frequency Interference (RFI) Reports. Report RFI investigations on the form designated for the type facility impacted by suspected interference.

13. Surveillance Inspection Reports. Report surveillance inspections on the appropriate facility form (e.g., ILS, VOR, LIGHTS, etc.).

14. Incomplete Inspection. When a crew is unable to complete an inspection, explain exactly what was inspected in the remarks, and the status. The crew completing the inspection may include these results on the final inspection report, and will include a remark referencing the incomplete inspection report(s).

15. ILS/MLS Maintenance Alert Report. In the event maintenance personnel are not on site during the ILS inspection, the flight inspection crew will submit ILS/MLS Maintenance Alert data to the FICO no later than the end of the duty day. The FICO will complete and submit the ILS/MLS Maintenance Alert Report within 24 hours of the inspection, as required by FAA Order 8200.1, Chapter 15, paragraph f, and in accordance with Appendix I of this Order.

16. AIRNAV Data Changes. Submit AIRNAV data changes as directed by FAA Order 8200.1, and in accordance with Appendix O of this Order. Explain in the remarks any data changes affecting the flight inspection (reference Chapter 3, paragraph 5.n).

17. Security Classification.

a. Guidance. The military organization requiring flight inspection report classification must provide guidance to FIS by letter or message. FIS must maintain this guidance to justify the initial classification determination (DOD 5200.1-R, Department of Defense Information Security Program Regulation).

b. Classification Markings. Flight inspection reports containing classified information must be marked in accordance with FAA Order 1600.2, National Security Information. Markings will show the degree of classification; name and routing symbol of the FAA employee applying the classification; authority for classification (reference to the military element's letter or message); safeguarding instructions and/or exemption category. If an exemption category is provided, the date when the report may be declassified will also be provided (if it can be determined). Specific marking instructions can be obtained from the servicing FAA security office. Do not list military unit designations or operational details in flight inspection reports.

Chapter 2. General Information › 18. Shipping Recorded Data.

8240.36N 08/30/2015

c. Report Control. Control, handling, storage, and transmission of classified flight inspection reports must be accomplished in accordance with FAA Order 1600.2.

d. Files. FIFO(s) must not maintain classified flight inspection facility report files. The Flight Inspection Records Team must contact the Civil Aviation Security Division, AMC-700, and obtain a security control number for all classified reports.

18. Shipping Recorded Data. The Mission Specialist will upload digital flight inspection data files directly into the Flight Operations Management System (FOMS) within one business day of return from a mission itinerary. The Mission Specialist will ship legacy flight inspection recordings (i.e., paper) to the Flight Inspection Records team no later than 15 days after the report reaches Stage 4 “Awaiting Recordings” (AR) status. Ship using the following guidance:

a. Securely tape a copy of the first page of the flight inspection report (draft or final) to the outside of the recordings or envelope, or annotate the following information on the cover page of each recording:

• Facility Identification and Type • Date(s) of Inspection • Type of Inspection, (e.g., C, S, P, PM, POA) • Aircraft Tail Number • Crew Member Numbers

b. Securely tape the recordings (all 4 sides) together. For a large stack of recordings, an envelope may be used.

c. Place a copy of the AIRNAV datasheets used, worksheets, and other required paperwork inside the recording folds. Include a copy of any data changes (FAA Form 8240-20), as applicable.

d. Ship in a box or fabric mailer. Do not use padded envelopes.

e. Include the contents listing with each shipment. The list will include facility idents, facility type, and the inspection date(s). Retain a copy of the contents listing and e-mail a copy to the Flight Inspection Records Team ([email protected]) . Discard the contents listing when the Flight Inspection Records Team confirms shipment receipt.

f. Shipment tracking is mandatory. Ship via USPS registered mail or FedEx to the following address:

U.S. Postal Service

FAA/ MMAC/ AJW-335A

ARB, Room 117 P.O. Box 25082

Oklahoma City OK 73125

FedEx

FAA/ MMAC/ AJW-335A

ARB, Room 117 6500 S. MacArthur

Oklahoma City OK 73169

8240.36N 08/30/2015

20. Report Distribution. › h. Radio Frequency Interference Report.

19. Lost Recordings Coordination. When recordings are lost or rendered unusable, the MS will complete Form VN200 8200-1, “Lost Recordings Coordination,” and submit to the Flight Inspection Records Team. The Flight Inspection Records Team will place the form in the recording storage in lieu of the missing recordings. The FICO may issue a Special inspection to replace the lost data, or confirm operational status by subsequent inspection. To access form VN200 8200-1, select “Forms” and “Lost Recordings Coordination” from the FIRPS main menu.

20. Report Distribution. The Flight Inspection Records Team is responsible for flight inspection report distribution, and will mail or e-mail archived reports to the owning and/or servicing organizations.

a. FAA-Owned Facility Reports. Distribute reports to the following:

(1) Service Area with facility jurisdiction

(2) Technical Operations with facility jurisdiction.

b. Military Reports. The Flight Inspection Program Services Group will maintain a list of DoD organizations requesting flight inspection services. The listing will include the organization name, location, point of contact phone number, and e-mail address. Distribute DoD reports to the requesting organization(s) on file.

c. International Reports. If the FAA has a Memorandum of Understanding or Agreement (MOU/MOA) with a Host Nation, distribute reports in accordance with the MOU/MOA, and/or send to the address provided by the customer.

d. Privately Owned Facility/IFP Reports. Distribute to the owning and/or servicing organization specified in the Memorandum of Agreement.

e. General Characteristics Reports. Distribute to the airport authority, military command, or designated organization responsible for the procedure or inspected item.

f. After Accident Reports. Within 14 days of the inspection, send the report, FAA Form 8240­ 14 “After-Accident Continuation Sheet,” and the two (2) preceding flight inspection reports which met periodic requirements to the Accident Coordinator/ Investigator listed on FAA Form 8240-14.

g. Controlling Obstacle Evaluation Report. Distribute to the National Flight Procedures Office.

h. Radio Frequency Interference Report. Distribute to the Spectrum Engineering Services Office.

1. Flight Inspection Report Header. › b. State & Ctry.

8240.36N 08/30/2015

Chapter 3. Common Report Information

1. Flight Inspection Report Header. Reports headers contain similar fields, most of which are automatically filled. The Pilot in Command (PIC) and Mission Specialist (MS) will review each prefilled block for accuracy, and make necessary corrections. Use the following guidance when completing the header block.

a. Ident. Enter the NAVAID, Instrument Flight Procedure, Route, FIX, or “Ident” as listed on the Flight Itinerary and DFL. The following specific guidance applies.

(1) NAVAID. Use the identifier listed on the AIRNAV datasheet. For ARSR facilities, use the identifier of the controlling ARTCC, with the appropriate alpha subcode. For example, Kansas City ARTCC identifier is ZKC, and the subcode may be “A” = ZKCA. For PAR facilities, enter the ident listed on the AIRNAV datasheet for the specific runway. Report only one runway identifier per PAR report.

(2) Procedure(s) or FIX. If grouped with a facility report, use the facility identifier. For RNAV procedures, use the identifier specified on the itinerary. Note: Amended RNAV procedures may include a decimal number identifier, corresponding to the revision (e.g., KDFW35C.03).

(3) Charted Visual Flight Procedure (CVFP). Use the airport identifier, as listed on the AIRNAV datasheet.

(4) Lighting Systems. Requires separate reports for each runway end inspected. The lighting system identifier will normally be the airport identifier (as listed on the AIRNAV datasheet) plus the runway number (e.g., KOKC35L). For general lighting not affiliated with a runway or approach (i.e., taxiways), use the airport identifier.

(5) Controlling Obstacle Evaluation. Use the airport identifier, as listed on the AIRNAV datasheet.

(6) Communications. Use the controlling facility identifier, as listed on the AIRNAV datasheet. For example, ZFW, KSLC.

b. State & Ctry. Select the appropriate state and country dropdown entry. Leave the STATE field blank if not in the U.S. The country must match the AIRNAV datasheet.

8240.36N 08/30/2015

c. Inspection Date(s). The inspection date is based on actual Coordinated Universal Time (UTC) and date(s) listed on the Daily Flight Log (DFL). Use the following examples:

1. Flight Inspection Report Header. › h. Insp Type.

Inspection Description Example

Single Day Inspection 02/01/201

Multiple, Consecutive Days 01/12-15/20

4

14

ple, Non-Consecutive Days 08/06, 08, 10/2014

ple, Consecutive & Non-Consecutive Days 09/30, 11/02-03/2014

Multi

Multi

d. Location.

(1) Ground-based Facility Reports (ILS, VOR, NDB, ASR, etc.). Enter the facility location as listed on the AIRNAV datasheet. If a radar facility has more than one location, and the locations do not fit in the field, place an asterisk and explain in the remarks. Do not confuse ASR antenna location with ASR scope location.

(2) IFPs Reported on a General Characteristics or RNAV form. The location is the city as listed on the Flight Inspection Procedure Control (FIPC) form.

(3) Routes and Stand-Alone Point-in-Space Fixes. Leave the location blank.

(4) Shipboard TACAN. Enter the ship name and hull number. For example, USS Princeton – CVL-23.

e. Runway. Applicable to PAR, ILS, MLS and RNAV reports only. Enter the runway listed in the SIAP title. For circling approaches, SIDs, or STARs, leave blank.

f. Category. Applicable to ILS and MLS reports only. Enter the category as specified on the AIRNAV datasheet (CAT I, II, or III).

g. Ctrl Number. This field (on the RNAV form only) is no longer used. List each applicable special control number in the remarks.

h. Insp Type. There are five basic flight inspection categories: Site Evaluation, Commissioning, Specials, Periodic, and Surveillance. Specials include Reconfiguration, After Accident, RFI, Scheduled, and Unscheduled inspections. Reports may include multiple inspection items, but must have a single inspection type code. The inspection type code may include one or more suffix code(s). Use Table 3-1 to determine the proper inspection type code and suffix(es). Give preference to the code highest on the list, to prevent essential data from being incorrectly purged from FIRPS. For example, a commissioning inspection supersedes a special inspection. Likewise, a reconfiguration special supersedes a scheduled special and/or periodic inspection.

NOTE: This hierarchy is not to be confused with the “Priorities of Flight Inspections,” listed in FAA Order 8200.1, Chapter 4.

8240.36N 08/30/2015

Table 3-1. Inspection Type Codes

NSPECTION TYPE CODES

E SITE EVALUATION

C COMMISSIONING INSPECTION

SPECIALS:

R Reconfiguration (Usually a commissioning type inspection)

h. Insp Type. › Table 3-1. Inspection Type Codes

A After Accident (Includes “Near Mid-Air” RADAR inspections)

Z Radio Frequency Interference

S Scheduled (Shipboard TACAN Special inspections are always “complete”)

U Unscheduled

P PERIODIC INSPECTION

V SURVEILLANCE INSPECTION (Surveillance Inspections are always “complete”)

UFFIXES

Incomplete Inspection: Indicates one or more inspection requirement is incomplete. Explain I in the remarks. NOTE: When the inspection is completed, all report requirements may be consolidated onto the final report. FOMS special control number remains “open.”

Unsatisfactory Procedure: Applies only to Instrument Flight Procedure inspections. Does not apply to facility inspections (VOR, ILS, ASR, etc.). Indicates the inspection requirement U is completed but unsatisfactory. FIS will return the procedure to the designer for rework. FOMS special control number is “closed.”

Changes to Procedure: Applies only to Instrument Flight Procedure inspections. Does not apply to facility inspections (VOR, ILS, ASR, etc.) Indicates the inspection requirement is C completed and satisfactory, so long as the listed changes are incorporated into the procedure prior to publication. An additional flight inspection is not required.

Gold Standard Procedure: Applies only to ARINC 424 coded Instrument Flight Procedures. Indicates the inspection requirement is completed and satisfactory in accordance with the G Flight Inspection Services Gold Standard process. NOTE: This suffix may be used in combination with the "Changes" suffix only when the changes will not affect the ARINC 424 coding.

I

S

Chapter 3. Common Report Information › 5. Remarks.

8240.36N 08/30/2015

2. Crew Information. Each form contains similar Crew Information blocks. Apply the following guidance, as applicable:

a. PIC, SIC, MS, and ACM. Enter the pilot-in-command (PIC), second-in-command (SIC), Mission Specialist (MS), and additional crew member (ACM) crew numbers (VN###), as applicable. If the MS did not record data during the inspection, “NA” may replace the MS crew number. The PIC and MS (when listed) certify the reported technical data is complete, accurate, and conforms to U.S. standards and specifications. The PIC certifies the operational status of the facility and the degree to which the facility supports the inspected instrument flight procedure(s).

(1) If the PIC was not the ASIP responsible for the inspection, list the ASIP crew number either in the ACM field or remarks block, with explanation.

(2) If the flight inspection was completed over multiple days with different crews, the data may be combined onto a single report. List the final PIC in block 2. The other PIC(s) and MS(s) may be listed (by position) along with their crew number in the remarks, with explanation.

(3) When a VOT is inspected using a portable ILS/VOR receiver, leave the PIC and SIC fields blank unless a NOTAM was issued as a result of the inspection. If a NOTAM was issued, enter the PIC crew number.

b. A/C NO. Enter the aircraft tail number (e.g., N34) as listed on the DFL. If multiple aircraft were used for the inspection, enter the final aircraft number in this block. List the other tail numbers in the remarks.

c. FIFO. Enter the PIC’s Flight Inspection Field Office (FIFO) 3-letter code, or “ARMY” if Army personnel accomplished the inspection. USAF Det 1 and 1-ASF will enter “OKC.” For other non-FAA inspections, enter “OTHER” and explain in the remarks.

3. Facility Information. Complete this block in accordance with the report-specific guidance contained in the appendices of this Order.

4. NOTAMs. List each issued, revised, or cancelled NOTAM (verbatim) as a result of the facility and/or IFP inspection, and the date. For military facilities/IFPs, list the recommended verbiage given to the military authority and the initials of the recipient, or list the NOTAM issued by the military. For unchanged, active NOTAM(s) remaining in effect, enter “Existing NOTAM remains in effect: [list existing NOTAM].”

5. Remarks. Use FAA Form 8240-1 “Continuation Sheet” if the inspection remarks will not fit in block 5. In addition to remarks required by FAA Order 8200.1, click on the “common remarks list” icon to select standardized remarks, as applicable.

5. Remarks. › b. SIAP(s) Verified.

8240.36N 08/30/2015

a. IFP Statement. For new, amended or changed IFPs (i.e., SIAP, SID, STAR, ODP, etc.) associated with an airport, add a remark including the following information:

FICO Control Number, Primary Airport, City, State (or Country), Procedure Name, Amdt (if applicable), and Status.

Examples:

- Special Number: OP-03-116-13. Huntsville Muni, Huntsville, AR, VOR/DME RWY 12,

Amdt 2, Sat.

- Special Number: BP-11-001-13. Sidney Muni, Sidney, OH, T/O Mins and ODP, Amdt 3,

satisfactory.

- Special Number: YP-09-148-13. Baltimore/Washington Int’l Thurgood Marshall, Baltimore,

MD, RIPKN ONE ARRIVAL, incomplete.

- Special Number: AP-06-386-13. Rutherford Co – Marchman Field, Rutherfordton, NC, T/O

Mins and ODP, Amdt 3, unsatisfactory.

- Special Number: YP-11-260-13. Norfolk Int’l, Norfolk, VA, KISSR TWO DEPARTURE,

satisfactory with changes to the ESV request.

b. SIAP(s) Verified. Use the “SIAP(s) Verified” field (or “Procedure Evaluation” fields on the RNAV report) to indicate the procedure was inspected in accordance with FAA Order 8200.1, Chapter 6. Leave the field blank when the procedure was inspected using other guidance (e.g., Contingency, Natural Disaster, or other) and explain in the remarks.

(1) Sat – SIAP(s) verified satisfactory in accordance with FAA Order 8200.1, Chapter 6.

(2) Sat/Unsat* – Multiple SIAPs inspected. Explain the status of each Unsat SIAP in the remarks.

(3) Sat/Unsat/Incomplete* – Multiple SIAPs inspected. Explain the status of each Unsat and Incomplete SIAP in the remarks.

(4) Sat/Incomplete* – Multiple SIAPs inspected. Explain the status of each Incomplete SIAP in the remarks.

(5) Unsat* – SIAP(s) not usable. Explain in the remarks.

(6) Unsat/Incomplete* – Multiple SIAPs inspected. Explain the status of each inspected SIAP in the remarks.

(7) -* – Explain in the remarks.

NOTE: Include an IFP statement in the remarks for new, changed or amended SIAPs; see paragraph 5.a. above.

5. Remarks. › g. Lighting Systems.

8240.36N 08/30/2015

c. Site Evaluation, NAVAID Commissioning, and Special Flight Inspection Reports. In addition to the FICO special control number, explain the reason for the inspection, ensuring remarks are consise and easy to understand. (e.g., “Reconfiguration for new FAS data and circling mins” or “Special for VOR antenna replacement.”) Explanations are not required for shipboard TACAN inspections.

d. Periodic Requirements. When a Special, Reconfiguration, or Surveillance type inspection meets periodic requirements, enter a statement in the remarks.

Examples:

- Periodic requirements met - Periodic with orbit requirements met - Periodic with monitors requirements met - LOC periodic with monitors met - GS periodic with monitors met - XMTR #1 – Periodic requirements met; XMTR #2 – Out of Service

NOTE: For After Accident inspections, reference Appendix L when updating periodicity.

NOTE: For OPSNET and/or specially designated “Night Inspection” airports/runways, the FICO schedules SIAP obstacle evaluations using the DFL code “ROC” (also known as the “A” check) during daylight hours, independent from nighttime periodic inspections. If periodic requirements were met during night ops, with the exception of the obstacle verification, remark “periodic requirements met, except for obstacle verification.”

e. SIAP required, but not inspected. Enter a remark identifying the name of the SIAP(s) and the statement, “required, but not inspected.” Give an explanation.

f. ARINC Coding Meets Gold Standard. If the ARINC coding passed the Flight Inspection Services Coding Preflight Validation (CPV) process, and was verified satisfactory by flight inspection, the INSP TYPE should contain a G suffix. This also applies when the procedure is “SAT w/Changes,” so long as the changes do not affect the ARINC coding.

g. Lighting Systems. Use the “Lighting Systems” field (if present) to report the status of alreadycommissioned lighting systems designed to support reduced visibility minima. These systems include Approach Light Systems (ALS), High Intensity Runway Lights (HIRL), Touchdown Zone Lights (TDZL), and Runway Centerline Lighting Systems (CL). Select SAT if the lighting system(s) safely supported the SIAP. Leave blank if this type lighting system is not installed, or was not inspected. If a hazard to safety was found, select UNSAT and enter a remark identifying the type lighting system and the discrepancy details. If a “Lighting Systems” field is not present and a hazard to safety was found, a remark is required (e.g., “MALSR Rwy 27, UNSAT; threshold light bar and RAIL inoperative”).

NOTE: Lighting System Commissioning, Reconfiguration, or Special inspections are reported on FAA Form 8240-5 (see Appendix D).

5. Remarks. › m. Narrative Remarks.

8240.36N 08/30/2015

h. Unsatisfactory Vertical Descent Angle (VDA). When VDA advisory guidance is unsatisfactory for obstacle clearance, but the remaining ARINC coding and SIAP are satisfactory, include the remark "SIAP verified SAT IAW FAA Order 8200.1, USSFIM, except VDA data must be removed from ARINC coding and not charted." Do not use the G suffix on the INSP TYPE, since the coding does not meet the Gold Standard. Include specific details about the location and description of the obstacle(s) penetrating the VDA. Coordinates are desirable, however distance from threshold and offset from centerline is acceptable.

i. Contingency or Natural Disaster Flight Inspection. For military contingency or natural disaster flight inspections, do not select “SAT” in the “SIAP(s) Verified” field. Instead, enter one of the following statements:

- SIAP(s) inspected IAW Military Contingency Flight Inspection Procedures

- SIAP(s) inspected IAW Natural Disaster Flight Inspection Procedures

j. No Electronic Data Required. When procedure changes do not require recorded data (Example: MDA raised; controlling obstacle changed with no minima change; fix added within the FISSV), include the statement, “No electronic data required.”

k. Reference Affiliated Reports. When multiple facilities are inspected, each affiliated with a common IFP but not grouped together on a single report, add a remark to each report. For example:

- ABC Report: “Reference XYZ report, 10/15/2014, for additional data.”

- XYZ Report: “Part of Special # OP-01-011-14, HAPPY 2 ARRIVAL. Reference ABC report, same date.”

l. Out-of-Tolerance Conditions.

(1) Identify and describe each out-of-tolerance or unsatisfactory condition. Where there is no provision to identify an out-of-tolerance condition (e.g., FAA Form 8240-2, Field 7), place a symbol next to the “as left” data. In the remarks, place a corresponding symbol and describe the condition and/or status (corrected/ uncorrected).

(2) Military Facilities. For an out-of-tolerance condition found on a military-owned facility or procedure, remark who the crew advised, the initials of military representative (if available), and the date (e.g., “Notified tower controller, “JB”, 04/26/2015”).

m. Narrative Remarks. Use factual statements and plain language when describing flight inspection results, restrictions, unsatisfactory conditions, unusable facilities/IFPs, etc. Do not go into detail regarding adjustments to obtain the final result (unless the inspection was an engineering project designed specifically to determine the effect of adjustments or facility configurations). Do not attempt to determine causal relationships based on observations. For example:

(1) Observation (Permissible): "The facility structure deteriorated at 210°. Crew observed inprogress highway construction southwest of the NAVAID toward the bad sector."

5. Remarks. › q. Weather Broadcast Information.

8240.36N 08/30/2015

(2) Unsubstantiated Conclusion (Prohibited): "Highway construction southwest of the NAVAID is causing course structure deterioration at 210°.”

n. Data Change Remarks. If the AIRNAV datasheet location, identifier and/or equipment changed, include a remark containing both the old and new information on the first report following the change. Explain the reason for the change, if known.

o. Expanded Service Volume (ESV). Include an ESV remark on the primary facility report. The remark should contain the inspection details, the fix name (if applicable), and whether the inspection was an original or revalidation ESV request. If unsatisfactory, provide an explanation.

(1) VOR/TACAN/NDB. List the facility ident, facility component/ azimuth (radial, or starting and ending radials bounding an arc)/ ESV distance (in NM)/ minimum ESV reception altitude (lower limit), and status. A TACAN ESV reported SAT implies both the azimuth and DME were satisfactory. However, if only one component of the TACAN is inspected, or the status differs between the azimuth and DME, create separate remarks for each component (i.e., TAC/DME or TAC/AZ). Report the ESV upper limit only if inspected (by request).

Examples:

“ESV: IRW / VOR / R-090 / 45.0NM / 16,000ft / Original / SAT”

“ESV: IRW / DME / R-090 / 45.0NM / 16,000ft / Revalidation / UNSAT. Numerous unlocks beyond 41.0 NM”

(2) LOC/GS/ILSDME. Both lower and upper limits are required for LOC, ILS-DME, and TLS ESVs. Azimuth is not required if the ESV extends along the LOC course.

Examples:

“ESV: LAX / LOC / “FUELR” fix / 27.0NM / 7,000-17,500ft / Orig / SAT”

“ESV: LAX / ILS-DME / “FUELR” fix / 27.0NM / 4,600-9,700ft / Revalidation / SAT”

“ESV: LAX / GS / 27.0NM / 8,100ft / Orig / SAT”

p. 75 MHz Marker Beacons. Document on the primary NAVAID report, (e.g., VOR, ILS, NDB).

(1) Commissioning and Reconfigurations. List each checklist item inspected and the status. If dual equipment is installed, document the minor axis width for both transmitters.

(2) Periodic Inspections. For non-ILS, enter a statement to indicate the marker was checked satisfactorily (Example: 75 MHz marker checked, SAT). For ILS, use the designated field in block 3.

q. Weather Broadcast Information. On commissioning reports only, list the weather broadcast capabilities for each facility inspected.

5. Remarks. › x. Other.

8240.36N 08/30/2015

r. Critical Area Interference Checks. When accomplished, add the remark “The FAA does not consider this flight inspection as a valid check of interference caused by aircraft/vehicles in the ILS critical zone.”

s. Structure Tolerance (95% Rule). Notify the FICO when the structure tolerance 95% rule is applied to a Category II/ III facility. The FICO must notify the applicable service area or military command engineering staff upon initial application of these criteria. Add the remark “FICO notified, 95% rule applied.” (Reference FAA Order 8200.1, Chapter 15).

t. MAGVAR Change Inspection. For rho-theta and NDB magnetic variation change inspections, add remarks detailing the published facility restriction, receiver checkpoint, and ESV radial changes based on the MAGVAR change. For example, a published coverage restriction of 210 ­ 250° would be changed to 214 - 254° after a MAGVAR change from 2° West to 6° West. Submit the appropriate changes to the Aeronautical Data Support Team on FAA Form 8240-20.

u. Completion of Previously Incompleted Inspection. Add a remark indicating the check completes the inspection requirements of the report dated mm/dd/yy. (Example: This completes the requirements for the inspection dated 02/11/02). (Reference Chapter 2, Paragraph 14.)

v. RFI Checks. Enter a narrative describing the reason for the inspection, checks performed, and the results obtained. Provide a physical description and latitude/ longitude of suspected interference source. For incomplete or unsuccessful checks, report bearings obtained, and aircraft location. Provide any information that may help another crew locate the RFI source.

w. 1800 RVR. When a CAT I ILS facility fails to support a SIAP authorizing approaches with 1800 RVR, using a Flight Director (FD), Autopilot (AP), or Heads-up Display (HUD) to the Decision Altitude (DA), include the remark, “System does not meet the 1800 RVR requirements. NOTAM issued through FICO, and Flight Inspection Technical Services Team notified (date)”. Include a copy of the NOTAM on the report.

x. Other. Reference the applicable appendix for additional required remarks.

8240.36N 08/30/2015

This Page Intentionally Left Blank

8240.36N 08/30/2015

Chapter 4. Quality Checklists

Use the following checklists as a quick reference when quality-checking reports in FIRPS. Crossreference applicable AIRNAV datasheets, DFLs, FOMS, and report line items during the QC process. If a discrepancy is found, reject the report with a comment explaining the reason, along with a reference.

Chapter 4. Quality Checklists › #1 - Report Header & Drew Information

Report Header & Crew Information … Checklist #1 Rho-Theta Systems … Checklist #2 GBAS … Checklist #3 NDB, DF, Lights, and Comm … Checklist #4 PAR … Checklist #5 ILS … Checklist #6 ASR/ ATCRBS … Checklist #7 General Characteristics … Checklist #8 MLS … Checklist #9 RNAV … Checklist #10

CHECKLIST #1

Applicable to most Flight Inspection Reports

BLOCK 1. FLIGHT INSPECTION REPORT HEADER

Reference: Chapter 3. Common Report Information

1. IDENT: Matches DFL and/or AIRNAV Datas 2. STATE & CTRY: Matches AIRNAV Datashe 3. INSPECTION DATE(S): UTC date matches 4. LOCATION: Matches AIRNAV Datasheet (no RUNWAY: Inspected runway number(s) for P 5. Note: Not applicable to SIDs, STARs or ODPs. 6. INSP TYPE: Matches DFL and includes correc

BLOCK 2. CREW INFORMATION

Reference: Chapter 3. Common Report Information

heet. et. STATE is blank when not in the USA. DFL.

t necessarily the airport name). AR/ ILS/ MLS/ RNAV SIAPs only.

t suffix (I, U, C, G)

PIC: Crew number matches DFL. If the PIC was not the ASIP in charge, ensure remarks 7. include details. 8. SIC: Crew number matches DFL. 9. MS: Crew number matches DFL. "NA" may replace crew number if no data was collected. 10. A/C NO: Matches DFL. 11. ACM: Crew number if essential to the inspection, not including maintenance personnel. 12. FIFO. PIC’s field office (e.g., OKC), ARMY, or OTHER

Chapter 4. Quality Checklists › #3 - GBAS

8240.36N 08/30/2015

CHECKLIST #2

RHO-THETA SYSTEMS (Form 8240-2)

BLOCK 3. FACILITY INFORMATION

Reference: Appendix B. Rho-Theta Systems

VOR, TACAN, VOT, DME Coverage, DME Accuracy: Inspected items selected. For 1. “Required, Not Inspected*,” ensure a remark exists. VOICE, STANDBY POWER and IDENT: Type voice inspected and status. Check 2. remarks for additional information. STANDBY POWER & IDENT: Status of inspected items. Check remarks for additional 3. information. FACILITY TYPE, FACILITY STATUS: Facility type matches AIRNAV datasheet. 4. Status is the “as left” condition. Remarks and NOTAMS reflect restrictions and/or additional information. SIAP(s) VERIFIED: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP 5. statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information.

CHECKLIST #3

GBAS (Form 8240-4)

LOCK 3. FACILITY INFORMATION

Reference: Appendix C. Ground-Based Augmentation System (GBAS). 1. PROFILE: Direction of flight. ALTITUDE: Minimum altitude or the highest and lowest altitudes, in the order checked 2. (altitude in ft/100; e.g., 2,000 ft listed as “20”). 3. RADIUS: Distance (NM) from reference point. 4. SIGNAL STRENGTH: Minimum field strength (dB). Dmax NM: Maximum use distance (tenths of NM), defined by GBAS facility. If restricted, 5. look for a remark. 6. GBAS FREQUENCY: Correct GBAS Frequency listed. 7. POLARIZATION: Type of polarization associated with the GBAS f acility. SIAP(s) VERIFIED: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP 8. statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information. FACILITY STATUS: “As Left” condition. Remarks and NOTAMS reflect restrictions 9.

B

and/or additional information.

Chapter 4. Quality Checklists › #5 - PAR

8240.36N 08/30/2015

CHECKLIST #4

NDB, DF, Lights, and Comm (Form 8240-5)

BLOCK 3. FACILITY INFORMATION

Reference: Appendix D. NDB, DF, Lights, and Communications.

DIRECTION FINDING, COMMUNICATIONS, VISUAL AIDS, NDB and NDB/ DME: 1. Indicates the facility/component inspected, and the inspection result. Those items not associated with the IDENT are blank, unless a discrepancy was reported (check remarks). FACILITY STATUS: “As Left” condition. Remarks and NOTAMS reflect restrictions 2. and/or additional information. SIAP(s) VERIFIED: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP 3. statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information.

CHECKLIST #5

PAR (Form 8240-6)

BLOCK 3. FACILITY INFORMATION

Reference: Appendix F. Precision Approach Radar (PAR).

CONTROLLER PERF: Matches inspection results. Blank if not required and not 1. inspected. Remarks reflect additional information, if necessary. ILS/ MLS/ VGSI COINC.: PAR glidepath is/is-not coincident with selected items. If not 2. inspected, then blank. Remarks reflect additional information, if necessary. STANDBY EQUIPMENT and STANDBY POWER: Status of inspection items. Blank if 3. not required and not inspected. Check remarks if required, but not inspected. LIGHTING SYSTEMS: ALS, HIRL, TDZL, and/or RCLS inspected. Blank if not installed 4. or not inspected. Check remarks if hazard to safety was found. FREQUENCIES USED: List of each frequency inspected. Remarks may include 5. frequencies if additional space was needed. FACILITY STATUS: “As Left” condition. Remarks and NOTAMS reflect restrictions 6. and/or additional information. PUBLISHED ANGLE, PUB. ALTERNATE ANGLE. Angles match AIRNAV datasheet 7. and Terminal Procedures Publication. 8. EQUIPMENT TYPE: Matches AIRNAV datasheet. SIAP(s) VERIFIED: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP 9. statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information.

Chapter 4. Quality Checklists › #6 - ILS

8240.36N 08/30/2015

CHECKLIST #6

ILS (Form 8240-8)

K 3. FACILITY INFORMATION

eference: Appendix H. Instrument Landing System (ILS).

LOCALIZER, OFFSET, GLIDESLOPE, LDA, SDF, TLS, Other*: Inspected items selected. For “Required, Not Inspected*” ensure a remark exists. TLS includes LOC and/or GS entries. See remarks for Other* remarks. DME: If not part of the ILS system, DME facility IDENT and TYPE is listed.Ensure DME inspection result is selected. COMPASS LOCATOR: Broadcasted IDENT and status. If more than one NDB is associated with ILS/LOC system, additional info is in the remarks. LIGHTING SYSTEM: ALS, HIRL, TDZL, and/or RCLS inspected. Blank if not installed or not inspected. Check remarks if hazard to safety was found. 75 MHz MARKERS: Selected if installed and inspected. If required/not inspected, check remarks for explanation. SIAP(s) Verified: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information. PUBLICATIONS: Status of Terminal Procedures Publications review. COMD WIDTH/ANGLE, GLIDE SLOPE TYPE: Matches AIRNAV datasheet. FACILITY STATUS (F/C, G/S, B/C): “As Left” condition. Remarks and NOTAMS reflect restrictions and/or additional information. ILS CLASS. SYS: - First Field (I, II, or III) matches AIRNAV datasheet. Note: Cat II & III have special requirements. See Appendix H. - Second Field (A/B/C/T/D/E) is the point where LOC conformed to CAT III structure tolerance.

BLOC

R

1.

2.

3.

4.

5.

6.

7. 8.

9.

10.

- Remarks contain additional information, as required. 11. INSP. CRITERIA: Entry if inspected to higher CAT standard, otherwise blank. 12. ROLLOUT: When performed/required, contains appropriate rollout code (S/U4/U5/R4/R5).

8240.36N 08/30/2015

Chapter 4. Quality Checklists › #7 - ASR/ ATCRBS

CHECKLIST #7

ASR/ ATCRBS (Form 8240-12)

LOCK 3. FACILITY INFORMATION

Reference: Appendix J. Surveillance Radar (ASR, ATCRBS).

ASR, ARSR, SECRA and MSAW: Inspected items selected. For “Required, Not 1. Inspected*” ensure a remark exists. 2. GROUND EQUIPMENT TYPE: Matches AIRNAV datasheet. SCOPE LOCATION: Matches AIRNAV datasheet. Ensure scope location is not confused 3. with RADAR location. 4. STANDBY POWER: Selected if inspected, otherwise left blank. FACILITY STATUS: “As Left” condition. Remarks and NOTAMS reflect restrictions 5. and/or additional information. SIAP(s) VERIFIED: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP 6. statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information. ANTENNA TILT: Primary and Secondary tilt matches AIRNAV datasheet (FIXED or 7. VAR) OPTIMUM ANGLE: Matches AIRNAV datasheet and/or inspected angle. If tilt is variable, 8.

B

may be blank.

Chapter 4. Quality Checklists › #9 - MLS

8240.36N 08/30/2015

CHECKLIST #8

General Characteristics (Form 8240-13)

BLOCK 3. FACILITY INFORMATION

Reference: Appendix K. General Characteristics. 1. AIRPORTS: Blank. (IDENT in BLOCK 1 should match airport reports) LIGHTING SYSTEMS: ALS, HIRL, TDZL, and/or RCLS inspected. Blank if not installe 2. or not inspected. Check remarks if hazard to safety was found. 3. OTHER (EXPLAIN)*: Systems other than lights inspected. Check remarks.

FACILITY TYPE and CLASS, SID, or UNNAMED DEPARTURE PROCEDURE: 4. ADS/B CVFP WAM Airport Markings/Signage Obstacle Departure Procedure Or use plain language to describe facility inspected 5. FACILITY STATUS: Blank. SIAP(s) VERIFIED: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP 6. statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information.

d

CHECKLIST #9

MLS (Form 8240-16)

BLOCK 3. FACILITY INFORMATION

Reference: Appendix M. Microwave Landing System (MLS).

FRONT AZIMUTH, BACK AZIMUTH, ELEVATION and DME: “As Left” condition. 1. Remarks and NOTAMS reflect restrictions and/or additional information. LIGHTING SYSTEM: ALS, HIRL, TDZL, and/or RCLS inspected. Blank if not installed 2. or not inspected. Check remarks if hazard to safety was found. 3. AZ CRS BRG and BAZ CRS BRG: Matches the SIAP course to the runway. 4. MGP: Minimum commissioned glide path angle. FACILITY STATUS (AZ, ELEV, BAZ): “As Left” condition. Remarks and NOTAMS 5. reflect restrictions and/or additional information. SIAP(s) VERIFIED: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP 6. statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information.

Chapter 4. Quality Checklists › #10 - RNAV

8240.36N 08/30/2015

CHECKLIST #10

RNAV (Form 8240-17)

BLOCK 3. FACILITY INFORMATION

Reference: Appendix N. Area Navigation (RNAV). 1. PROCEDURE TYPE: Abbreviation for the RNAV type inspected. 2. PROCEDURE NAME: Matches published procedure title. PROC MODIFIED: “YES” if procedure modification was necessary, otherwise “NO.” 3. A remark is required if modified. 4. SENSOR STATUS: Status of RAIM, WAAS, or LAAS. 5. ARINC 424 CODING: Status of ARINC 424 CPV and Flight Inspection validation. ADD. RUNWAYS: Airport identifiers & additional runways, if there is insufficient space in 6. Block 1. Note: Not applicable to SIDs, STARs or ODPs. 7. CRC: (LPV & LP only) Matches 8260-10, FAS Data Block Information. CRS ERROR: (LPV & LP only) AFIS-computed course alignment error (e.g., R0.02 or 8. L0.01). 9. RNP: (RNP approaches only) Most critical RNP v alue inspected. 10. WAAS HPL: (LPV & LP only) Highest HPL in tenths of a meter. 11. WAAS VPL: (LPV only) Highest VPL in tenths of a meter. 12. GEO SNR: (LPV & LP only) Lowest GEO SNR in the final approach segment (dB). FAS VERT. P.A. (Comm): (LPV & LNAV/VNAV only) Commissioned vertical path angle 13. (tenths of a degree) matches 8260-10, FAS Data Block Information, or 8260-3, Procedure Form. 14. FAS VERT. P.A. (Actual): (LPV only) Actual vertical path angle (tenths of a degree). TCH (Comm): (LPV and LNAV/VNAV only). Commissioned TCH matches 8260-10, FAS 15. Data Block Information or 8260-3 Procedure Form. 16. TCH (Actual): (LPV only). Actual TCH (tenths of a ft). PROCEDURE EVALUATION (HUMAN FACTORS, OBSTACLE VERIF., COMM,

17. and PROC. FLYABILITY: Selected if inspected IAW 8200.1, Chapter 6. Remarks include IFP statement for new/amended procedures. Remarks reflect Unsat, Incomplete, or Other status information.

18. LIGHTING SYSTEMS: ALS, HIRL, TDZL, and/or RCLS inspected. Blank if not installed or not inspected. Check remarks if hazard to safety was found.

8240.36N 08/30/2015

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms

Appendix A. FAA Flight Inspection Report Forms

Flight inspection report forms are computer generated in FIRPS. When FIRPS is inaccessible, manually produce the appropriate form and submit to the Flight Inspection Records Team. Manually created reports are considered temporary until electronically transferred into FIRPS.

Form Version Flight Inspection Report Title

8240-1 07/05 CONTINUATION SHEET (Compatible with all reports; select the (+) icon to add.)

8240-2 08/15 RHO-THETA SYSTEMS

8240-4 08/15 GBAS

8240-5 08/15 NDB, DF, LIGHTS, and COMM

8240-6 08/15 PRECISION APPROACH RADAR

- GENERIC PAR Continuation Sheet

- GPN-22 or TPN-25 PAR Continuation Sheet

- TPN-22 PAR Continuation Sheet

8240-7 07/05 ILS WORKSHEET

8240-8 08/15 ILS

8240-11 08/15 ILS/MLS MAINTENANCE ALERT

8240-12 08/15 SURVEILLANCE RADAR

8240-13 08/15 GENERAL CHARACTERISTICS

8240-14 08/15 AFTER ACCIDENT CONTINUATION SHEET

8240-16 08/15 MLS

8240-17 08/15 RNAV

8240-20 05/11 DATA CHANGE SUBMISSION

8240-21 08/15 OBSTACLE EVALUATION

8240-23 08/15 PRM/FMA

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › 8240-1 CONTINUATION SHEET

FLIGHT INSPECTION REPORT

CONTINUATION SHEET

5. REMARKS (con!' d)

This Page Intentionally Left Blank

FLIGHT INSPECTION REPORT

Rho-Theta Systems

1. FLIGHT INSPECTION REPORT HEADER 2. CREW INFORMATION

PIC SIC MS NCNO I II II II I

riD::.:E::.cN.:..:T … --, STATE CTRY INSPECTION DATE(S) ~~------~1~1 ~11~~11~----------~1

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-2

LOCATION INSP TYPE ACM FIFO I II I II I

3. FACILITY INFORMATION

VOR I I FACILITY STATUS I I VOICE TACAN I I SIAP(s) VERIFIED I I VOT STANDBY POWER

DME COV. I DENT

DME ACC. FACILITY TYPE

4. NOTAMs

5. REMARKS

6. FLIGHT INSPECTION DATA

A. ORBITAL DATA

MEAN MAX+ MAX· SPREAD DIR ALT DIST REF DATE

TX1

TX 2

TP1

TP 2

B. REFERENCE RADIAL/MONITORS

OVOR OVOT TX ALIGN ALARM ALARM DATE ESTABLISHED

REFERENCE RADIAL I

I CHECK POINT I

TAC TP ALIGN ALARM ALARM DATE ESTABLISHED +

REFERENCE RADIAL I

I I CHECK POINT I

• Remarks are required for fields marked with an asterisk

FAA Form 8240-2 (08-15) Supersedes Previous Edition PAGE 1 OF3

7. VOR, VORIDME, VORTAC, TACAN, VOT- RADIAL DATA

Service Designation

Radial Use

P.zimuth

ransmitter(s)

MSL Altitude

Distance From

Distance To

oughness/Scalloping

Bend/CMA

Bends

Polarization

P.llgnment Error

Modulations

ransmitter Diff.

Signal Strength

nterference

Service Designation

Radial Use

1\zimuth

ransmitter(s)

MSL Altitude

Distance From

Distance To

Roughness/Scalloping

Bend/CMA

Bends

Polarization

lignment Error

Modulations

ransmitter Diff.

Signal Strength

nterference

Service Designation

Radial Use

zimuth

ransmitter(s)

MSL Altitude

Distance From

Distance To

Roughness/Scalloping

Bend/CMA

Bends

Polarization

P.lignment Error

Modulations

ransmitter Diff.

Signal Strength

nterference

• Remarks are required for fields marked with an asterisk

FAA Form 8240-2 (08-16) Supersedes Prev1ous EditiOn PAGE 2 OF 3

08/30/2015

8240.36N Appendix A

8. VOR, VOR/DME, VORTAC, TACAN, VOT - ORBITAL DATA

A. TRANSMITTER NO

TRANSMITTER 1 TRANSPONDER 1

TRANSMITTER 2 TRANSPONDER 2

B. DME DISTANCE UNLOCK

C. TACAN AZIMUTH UNLOCK

D. AREA OF INTERFERENCE

E. VOR AZIMUTH EXCEEDS 2.5 DEGREES

00 10 20 30

120 130 140 150

240 250 260 270

40

160

280

50

170

290

60

180

300

70

190

310

80

200

320

90

210

330

100 110

220 230

340 350

F. TAC AZIMUTH EXCEEDS 2.5 DEGREES

00 10 20 30

120 130 140 150

240 250 260 270

40

160

280

50

170

290

60

180

300

70

190

310

80

200

320

90

210

330

100 110

220 230

340 350

G. VOR COVERAGE SIGNAL STRENGTH (DOCUMENT LEVELS BELOW -93dbm OR 5 uV)

00 10 20 30

120 130 140 150

240 250 260 270

40

160

280

50

170

290

60

180

300

70

190

310

80

200

320

90

210

330

100 110

220 230

340 350

H. TACAN COVERAGE - SIGNAL STRENGTH (AT WHICH AZIMUTH OR DISTANCE UNLOCK OCCURS)

00 10 20 30

120 130 140 150

240 250 260 270

40

160

280

50

170

290

60

180

300

70

190

310

80

200

320

90

210

330

100 110

220 230

340 350

* Remarks are required for fields marked with an asterisk

FAA Form 8240-2 (08-15) Supersedes Previous Edition

PAGE 3 OF 3

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-4

I

I

FLIGHT INSPECTION REPORT

GBAS … IDE NT STATE CfRY INSPlcnON DATE!SJ ICJCJI

LOCATION

•

PROFILE ALTITUDE RADIUS SIGNAL DMAXNM I StRENGTH

GBAS FREQUENCY I

POLARIZATION I .

FAA Form 8240-4 (08-15) Supersedes Previous Edition

.. . PIC SIC MS AJCNO I c::::::::J c::::::::J c::::::::J I I INSPTYPE ACM FIFO II I II I .. .

I SIAP(I) VERIFIED I I I FACIUTY STATUS I I I

PAGE 1 OF2

FLIGHT INSPECTION REPORT

GBAS

RUNWAY AIRPORTID LOWERUMIT UPPER LIMIT

RUNWAY AIRPORTID CRC CHANNEL

FAA Form 8240-4 (08-15) Supersedes Previous Edition

" .

LEFT LIMIT RIGHT LIMIT MISSED ROLLOUT CVGMVA CVGUSV

.. .

RPI COURSE ALIGNMENT GLIDE PATH TCH

PAGE' 2 OF 2

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-5

FLIGHT INSPECTION REPORT NDB, DF, Lights, and Comm

1. FLIGHT INSPECTION REPORT HEADER 2. CREW INFORMATION IDENT STATE CTRY INSPECTION DATE(S) PIC SIC MS AVC NO N/A LOCATION INSP TYPE ACM FIFO

3. FACILITY INFORMATION DIRECTION FINDING NDB FACILITY STATUS COMMUNICATIONS NDB/DME SIAP(s) VERIFIED VISUAL AIDS

4. NOTAMs

5. REMARKS

6. FLIGHT INSPECTION DATA

A. NONDIRECTIONAL BEACON

RADIO CLASS CODE IDENTIFICATION INTERFERENCE VOICE FREQUENCY COVERAGE OSCILLATIONS BRG ACCURACY DME CHANNEL STA PASSAGE STANDBY EQUIP. STANDBY POWER

B. DIRECTION FINDING STATION PASSAGE STANDBY POWER CHECKPOINT AIRCRAFT ALTITUDE DISTANCE AIRCRAFT AIRCRAFT BEARING DF ERROR FREQUENCY USED

C. VISUAL AIDS FACILITY INSPECTED ALS REIL VASI PAPI OTHER*

SERVED RUNWAY(S) INTENSITY FLASHERS SEQUENCE ADJUST. FOCUS AND LIGHTS RUNWAY G.S. ANGLE ANGULAR OBST. CLEAR. COINC. RADIO CTRL COVERAGE (VGSI) (PAR/ILS/MLS) SYST.

D. COMMUNICATIONS

APPROACH CONTROL FSS TOWER CENTER OTHER* P/F CS/T

FREQUENCY USED PRIMARY SECONDARY QUALITY VOICE COVERAGE STANDBY POWER

* Remarks are required for fields marked with an asterisk FAA Form 8240-5 (08-15) Supersedes Previous Edition PAGE 1 OF 1

This Page Intentionally Left Blank

FLIGHT INSPECTION REPORT

PRECISION APPROACH RADAR

--------------------------------------------------------- 1. FLIGHT INSPECTION REPORT HEADER 2. CREWINFORMATION

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-6

I DENT STATE COUNTRY INSPECTION DATE(S) PIC SIC MS NCNO II II II II II

LOCATION RUNWAY INSPTYPE ACM FIFO II I I II … ,_ ---~---~-~-~~--·-~~~-~~,-------------------------------

3. FACILITY INFORMATION

CONTROLLER PERF FREQUENCIES USED FACILITY STATUS

FOUND SAT

I I

ILS/MLSNGSI COlli C. PUBLISHED ANGLE

STANDBY EQUIPMENT PUB ALTERNATE ANGLE

FOUND UNSATI I

STANDBY POWER EQUIPMENT TYPE

LIGHTING SYSTEMS SIAP(s) VERIFIED

4. NOTAMs

5. REMARKS

-------------------------------------------------------------------------------------· 6. FLIGHT INSPECTION DATA

A. AZIMUTH RADAR PRIMARY TX STBYTX B. ELEVATION RADAR PRIMARYTX STBYTX

COURSE ALIGNI\IENT I I I I GLIDE SLOPE ALIGNMENT I II I DEVIATION ACCURACY I I I I RANGE ACCURACY I II I RANGE ACCURACY I I I I COVERAGE I II I COVERAGE/USABLE OIST I I I I *Remarks are required for fields marked with an asterisk

FA A Form 8240-6 (08-15) Supersedes Previous &Jifion PAGE10F4

GENERIC PAR Continuation Sheet

FAA Form 8240-6 (08-15) Supersedes Previous &Jifion

Runway

7. GENERAL

PAGE20F4

GPN-22 or TPN-25 PAR

Continuation Sheet

7. GENERAL

Runway

---------------------------------------------------------------------------------- 8. COMPUTER GENERATED PRECISION APPROACH RADAR RUN CONFIGUATIONS

TRACK FTC MTI

Run MODE RCVR TX ANGLE RUN CHECKS CHAN USED "SAT"

NOR BK UP ON OFF COH NON. OR c p

COH "UN SAT"

''A'' CURSOR PRIMARY ·o 0 ·o 0 ·o 0 A X X

''A'' CURSOR PRIMARY 0 ·o 0 "0 0 ' 0 A X

''A'' CURSOR BK UF RC ·o 0 '0 0 '0 0 B X X

''B'' CURSOR BKUF RC ·o 0 ·o 0 ·o 0 B X X

''B'' CURSOR PRIMARY ·o 0 ·o 0 ·o 0 A X

STANDBY TX CHECK ·o 0 ·o 0 ·o 0 A X

BK UP DATABASE 'A' CSR ·o 0 ·o 0 ·o 0 A X

BK UP DATABASE 'A'' CSR 0 ·o 0 "0 0 '0 A X

BK UP DATABASE 'B'' CSR ·o 0 '0 0 '0 0 A X

AI. ONLY APCH ·o 0 ·o 0 ·o 0 A X

ALTERNATE ANGLE "A" CSR ·o 0 ·o 0 ·o 0 A X

R Denotes requred oonfgumon ----------------------------------------------------------------------------------

FAA Form 8240-6 (08-15) Supersedes Previous Edition

9. OTHER INFORMATION

A. Receiver Sensitivity

NOR

Non-COH

COH

B. Clutter (Rain) Reject

Yes

No

N/A

C Transmitter Power (db)

D. Usable Range on Radar

E Firmware

Part#

Version#

F Digital MTI Baseline

Limiting Settings

PAGE 30F 4

TPN-22 PAR Continuation Sheet

Runway

System Serial#

8. COMPUTER GENERATED PRECISION APPROACH RADAR RUN CONFIGUATIONS

MTI CFAR ALS PAR AZIMUTH RUN MODE 46-DEG SECTOR USABLE ANGLE DISTANCE ON OFF ON OFF AUTO MANUAL ON 0 ·o 0 ·o ·o D . 0 A "A"CURSORAUTO . . . . B. "B"CURSORAUTO 0 D 0 0 0 D 0 . C "A" CURSOR AUTO D D D . D . D D . D . . . . D. "B" CURSOR AUTO D D D D D D D . . . . E "A" CURSOR MANUAL D D D D D D D . . . . F "A" CURSOR MANUAL 0 D 0 0 0 D 0

ALTERNATE TOUCHDOV\n'll POINTS ON SAME RUNWAY HEADING . . . .

G. "A" CURSOR AUTO D D D D D D D . . . . H. "A" CURSOR MANUAL 0 D 0 0 0 D 0 . . . . I. "B" CURSOR lviANUAL 0 D 0 0 0 D 0

AZIMUTH ONLY PROCEDURE . . . .

J. N. ONLY APPROACH D D D D D D D

R Denotes n?:QUired oon1gurabon

9. PROGRAM DATA

A Name

B Part Number

C Version

D. Build Date

E. Transmitter Output Power

F Receiver Sensitivity

FAA Form 8240-6 (08-15) Su,:.er:sedes Pre'fious Edition

CHECKS

"C" "P"

X X

X X

X X

X X

X

X

X X

X X

X X

X

PAGE40F4

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-7

FLIGHT INSPECTION REPORT -- ILS WORKSHEET

1. LOCATION: 2. IDENT:

3. RUNWAY NO: 4. DATE(S) OF INSPECTION: 5. OWNER:

6. TYPE OF INSPECTION: SITE EVALUATION PERIODIC SPECIAL COMMISSIONING SURVEILLANCE INCOMPLETE 7. FACILITY LOCALIZER SDF GLIDE SLOPE 75 mHz MARKERS DME INSPECTED: LDA TLS LIGHTING SYSTEM COMPASS LOCATORS OTHER 8.FACILITY STATUS F/C G/S B/C 9. LOCALIZER DATA 10. GLIDE SLOPE DATA UNRESTRICTED WIDTH CAT ANGLE CAT B S H L RESTRICTED DUAL FREQ DUAL TX GS TYPE VOICE ESV DUAL TX ESV UNUSABLE BACK CRS Y/N N (B 7.02 / S 2.49) GND TEMP OAT BARO ALT 11. NOTES: LOC - TH

12. RUN # CFG PA or ALN 150 CLR (Corrected) PA 90 CLR/Z1 SBP PW or CW Z2 SYM Z3 MOD Z4 REMARKS: Z5/POL

FAA Form 8240-7 (v1.0 7-2005) Supersedes previous edition Page 1 of 2

08/30/2015

IDENT:

8240.36N

Appendix A

FLIGHT INSPECTION REPORT -- ILS CONTINUATION WORKSHEET

1. NOTES:

12. RUN#

CFG

PA or ALN PA SBP 150 CLR (Corrected) 90 CLR/Z1

PW or CW Z2

SYM Z3

MOD Z4

REMARKS: Z5/POL

FAA Form 8240-7 (v1.0 7-2005) Formerly 8240-7-1

Page 2 of 2

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-8

I

FLIGHT INSPECTION REPORT

ILS

1. FLIGHT INSPECTION REPORT HEADER

I DENT STATE CTRY INSPECTION DATE(S)

II II II LOCATION RUNWAY CATEGORY l Jl II

INSP TYPE II

3. FACILITY INFORMATION

LOCALIZER DME

OFFSET COMPASS LOCATOR

GLIDE SLOPE LIGHTING SYSTEM

LOA 5 mHz MARKERS

SDF SIAP(s) VERIFIED

TLS PUBLICATIONS

OTHER*

COMO WIDTH

COMO ANGLE

GLIDE SLOPE TYPE

4. NOTAMs

5. REMARKS

2. CREW INFORMATION

PIC SIC MS NC NO I I II II II I ACM FIFO I II Jl I

FACILITY STATUS

F/C

G/S

B/C

ILS CLASS. SYS.

INSP. CRITERIA

ROLLOUT

* Remarks are required for fields marked with an asterisk

FAA Form 8240-8 (08-15) Supersedes Previous Edition PAG£1 OF 4

6. INSTRUMENT LANDING SYSTEM DATA -AZIMUTH (PART I)

A. FRONT COURSE B. BACK COURSE

ILS-1 ALTITUDE I I ILS-1 ALTITUDE I I

TX1 TX2 TX 1 TX2

CD INITIAL FINAL CD INITIAL FINAL CD INITIAL FINAL CD INITIAL FINAL

Course Width curse Width

Symmetry ymmetry

Modulation lllodulation

learance 150 learance 150

learance 90 learance 90

Structure-Z 1 tructure-Z 1

Structure-Z 2 tructure-Z 2

Structure-Z 3 tructure-Z 3

Structure-Z 4

Structure-Z 5

Vert. Polar. ert. Polar.

Alignment llgnment

dentlflcatlon dentlflcatlon

Power Ratio

oc Only Structure

7. INSTRUMENT LANDING SYSTEM DATA- GLIDE SLOPE (PART I)

IL5-2 ALTITUDE I I TX 1 TX 2

CD INITIAL FINAL CD INITIAL FINAL

Angle

Modulation

Width

Structure Below Path

Symmetry

Structure-Z 1

Structure-Z 2

Structure-Z 3

Angle Alignment "B-C"

Angl e Alignment "C-r'

Angle Alignment 'T'

8. INSTRUMENT LANDING SYSTEM DATA - MARKER WIDTH(s)

A OM

B. MM I

C. IM I

• Remarks are required for fields marked with an asterisk

FAA Form 8240-8 (08-15) Supersedes Previous Edition PAGE 2 OF4

9. INSTRUMENT LANDING SYSTEM DATA - AZIMUTH (PART II)

A. FRONT COURSE TX1 TX 1 TX 1 TX 2 TX 2 TX 2 B. BACK COURSE TX1 TX 1 TX 1 TX 2 TX2 TX 2 MONITOR CD INITIAL FINAL CD INITIAL FINAL MONITOR CD INITIAL FINAL CD INITIAL FINAL

Usable Dis./PVvt" Setting Usable Dis./PVvt" Setting

Course Width (Wide) Course Width (Wide)

Clearance 150 Clearance 150

Clearance 90 Clearance 90

Course Width (Narrow) Course Width (Narrow)

Clearance 150 Clearance 150

Clearance 90 Clearance 90

Alignment R

Alignment L

10. INSTRUMENT LANDING SYSTEM DATA- GLIDE SLOPE (PART II)

PATH ANGLE PATH WIDTH STRUCTURE BELOW PATH

TX 1 TX2 TX 1 TX 1 TX 2 TX2 TX1 TX1 TX2 TX2 TX1 TX1 TX2 TX2 INI11AL FINAL INITIAL FINAL INITIAL FINAL INITIAL FINAL INITIAL FINAL INITIAL FINAL

A. ANTENNA ADVANCE

DEPHASE RETAR[

B. MAIN SIDEBAND ADVANCE

DEPHASE RETAR[

c. PATH ANGLE LOWERED TO LIMIT

D. PATH ANGLE RAISED TO LIMIT

E. PATH WIDTH NARROWED TO LIMIT

F. PATH WIDTH WIDENED TO LIMIT

G. ATTEN. MIDDLE ANT TO LIMIT

H. A TTEN. UPPER ANTTO LIMIT

TX1 TX 2 N. MEAN WIDTH/SYMMETRY

I. USABLE DISTANCE I PWR SET. TX ~NGLEABOVE

J . CLEARANCE BELOW PATH ~NGLE BELOW

K. MODULATION EQUALITY fMDTH

L. PHASING ~YMMETRY

M. Front Course Area Where Phasin g Was Conducted 0. TILT

NM MSL TX ~ 50H z 90Hz

P. BEST FIT STRAIGHT LINE R. TRANSVERSE STRUCTURE TX1 uA TX1 Hz TX2 uA TX2 Hz

ARDH I GPI/TH DIS. I RDH I AIM PTELEV OFFSET RADIUS ALT ~EFT OF CL I I I fiGHT OF CL

Q. GLIDE SLOPE AIMING POINT ~- RADIO ALTIMETER

LATITUDE LONGITUDE

I

* Remarks are required for fields marked with an asterisk

FAA Form 8240-8 (08-15) Supersedes Previous Edition PAGE30F4

11. INSTRUMENT LANDING SYSTEM DATA -TRANSVERSE STRUCTURE PLOT

A. ANTTYPE I I D. CFG I I G. FLT DIRECT.

B. SITE ELEV. I I E. ALT I I H. GSWIDTH

C. TX I I F. RADIUS I II. GSANGLE

J. DEGREES FROM LOC-CL ABEAM GOP (DEGREES)

LOCALIZER- 90 Hz OCALIZER ·90Hz OCALIZER ·150 Hz LOCA LIZER • 150 Hz

12.0 .5 0.0 6.5

11.5 .0 0.5 7.0

11.0 .5 1.0 7.5

10.5 .0 1.5 8.0

10.0 .5 2.0 8.5

9.5 .0 2.5 9.0

9.0 .5 3.0 9.5

8.5 .0 3.5 10.0

8.0 .5 4.0 10.5

7.5 .0 4.5 11 .0

7.0 0.5 5.0 11 .5

6.5 0.0 5.5 12.0

6.0 6.0

K.

LOCALIZER - 90 Hz DEGREES FROM LOC-CL ABEAM GOP LOCALIZER- 150 Hz

150 150

120

GS 90

90Hz 60

cn~ 48 w~ a::= 30 wCD D.UI ::::E.E

0 gl! 0 a::e ~CI) 30 :E.!:!.

60 64 GS 150 Hz 90

120

150 150

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

• Remarks are required for fields marked with an asterisk

FAA Form 824041 (08-15) Supersedes Previous Edition PAGE 4 OF4

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-11

FLIGHT INSPECTION REPORT

ILS/MLS MAINTENANCE ALERT

1. FLIGHT INSPECTION REPORT HEADER

riD~E~N~T … ,rS~T~AT~E~,rC~T~R~Y __ ,riN~S~P~EC~T~IO~N~DA~T~E~(S~)-----------, ~~----~1~1 __ ,1~1~11~--------~1

LOCATION INSPTYPE I II I

3. FACILITY INFORMATION

4. NOTAMs

5. REMARKS

6. FLIGHT INSPECTION DATA

PARAMETER

ALERT RECEIVED BY I

PIC I

ACM I

* Remarks are required for fields marked with an asterisk

FAA Form 8240-11 (08-15) Supersedes Previous Edition

2. CREW INFORMATION

SIC MS NCNO II II II I FIFO II I

=OR>60% OF Fl

TOLERANCE

I

PAGE10F1

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-12

FLIGHT INSPECTION REPORT SURVEILLANCERADAR

1. FLIGHT INSPECTION REPORT HEADER 2. CREW INFORMATION IDENT STATE CTRY INSPECTION DATE(S) PIC SIC MS AVC NO N/A LOCATION INSP TYPE ACM FIFO

3. FACILITY INFORMATION

ASR GROUND FACILITY STATUS ARSR EQUIPMENT TYPE SIAP(s) VERIFIED SECRA SCOPE LOCATION ANTENNA TILT PRI SEC MSAW STANDBY POWER OPTIMUM ANGLE

4. NOTAMs

5. REMARKS

6. FLIGHT INSPECTION DATA

A. FIX COVERAGE FIX NAME AIRWAY ALTITUDE CHANNEL SAT/UNSAT FIX NAME AIRWAY ALTITUDE CHANNEL SAT/UNSAT

B. FIX TARGET IDENT/ORIENTATION CHECK POINT CHECK CHANNEL AZIMUTH DISTANCE POINT RADAR CHART RADAR CHART

C. ROUTE COVERAGE ROUTE FROM TO CHAN ALT POLAR MTI SECRA SAT/UNSAT

D. SURVEILLANCE APPROACHES AIRPORT RWY APPROACH CONDITION POS - MAP POLAR MTI CHAN SAT/UNSAT NM NM NM NM NM NM *Remarks are required for fields marked with an asterisk FAA Form 8240-12 (08-15)Supersedes Previous Edition PAGE 1 OF 1

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › FAA Forms 8240-13

08/30/2015

FLIGHT INSPECTION REPORT GENERAL CHARACTERISTICS

8240.36N Appendix A

2. CREW INFORMATION

1. FLIGHTINSPECTION REPORT HEADER IDENT STATE CTRY INSPECTION DATE(S) PIC SIC

LOCATION INSP TYPE ACM

3. FACILITY INFORMATION

AIRPORTS FACILITY TYPE AND FACILITY STATUS CLASS, SID, OR LIGHTING SYSTEMS UNNAMED DEPARTURE SIAP(s) VERIFIED OTHER (EXPLAIN)* PROCEDURE

4. NOTAMs

5. REMARKS

6. FLIGHT INSPECTION DATA

A. OUT OF TOLERANCE CONDITIONS FOUND (Except those covered by previous NOTAM)

B. Was a NOTAM issued based on the results of this inspection?

C. Is there a previous NOTAM in effect?

* Remarks are required for fields marked with an asterisk FAA Form 8240-13 (08-15) Supersedes Previous Edition

MS AVC NO N/A FIFO

CORRECTED

PAGE 1 OF 1

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-14

08/30/2015

FLIGHT INSPECTION REPORT AFTER ACCIDENT CONTINUATION SHEET

A. Location

B. Ident

C. Facility Type

D. Date(s) of Inspection

E. Date & Time of Accident

F. Aircraft Type & Number

A. Procedures In Use at Time of Accident

B. Equipment In Use at Time of Accident

C. Date & Time of After Accident Inspection

D. Weather Conditions at Time of Inspection

E. Procedures Inspected and Extent of Inspection

F.SIAP

G. Name & Routing Symbol of Accident Coordinator/Investigator

FAA Form 8240-14 (08-15) Supersedes Previous Edition

8240.36N Appendix A

1.GENERAL

2. OTHER INFORMATION

3. REMARKS

PAGE 1 OF 1

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-16

FLIGHT INSPECTION REPORT

MLS

1. FLIGHT INSPECTION REPORT HEADER

,.:.ID~E::.:N.:..:T … __, ,.:: S:..:; TA ~T:..::E: … ,,.:: C'-'- TR'-'-Y '-----, INSPECTION DATE(S) 11 … … 11 II 1'---1 -------'

rL~ O~CA ~T~IO~N~-----------...,rR~U~N~ W~AY~_,,rC~A~T=EG~O~R'-'-Y'----, INSP TYPE I II II II 3. FACILITY INFORMATION

FRONT AZIMUTH DME

BACK AZIMUTH LIGHTING SYSTEM

ELEVATION AZ CRS. BRG.

BAZ CRS. BRG.

MGP

4. NOTAMs

5. REMARKS

2. CREW INFORMATION

PIC SIC MS NC NO I II II II I ACM FIFO I II I

FACILITY STATUS

AZ

ELEV

BAZ

SIAP(s) VERIFIED

• Remarks are required for fields marked with an asterisk

FAA Form 8240·16 (08·15) Supersedes Previous Edition PAGE 1 OF 3

6. MICROWAVE LANDING SYSTEM DATA - AZIMUTH

A. FRONT TX 1 TX 2 .B. BACK TX1 TX2 AZIMUTH AZIMUTH OT INITIAL FINAL OT INITIAL FINAL OT INITIAL FINAL OT INITIAL FINAL

MCE MCE

PFE PFE

PFN PFN

CMN CMN

OCI OCI

Clearance Clearance

Basic Data Basic Data Words Words

Aux Data Aux Data Words Words

Prop Guid-L. Prop Guid-L.

Prop Guid-R. Prop Guid-R.

Identification identification

Usable Usable Distance Distance

MONITOR MONITOR

MCE-L. Ref. MCE-L. Ref.

PFE L. Align. PFE L. Align.

MCE-R. Ref. MCE-R. Ref.

PFE R. Align. PFE R. Align.

7. MICROWAVE LANDING SYSTEM DATA- RUNWAY AZIMUTH

TX 1 TX2 TX1 TX2 A. ZONE4 B . ZONES OT INillAL FINAL OT INITIAL FINAL OT INillAL FINAL OT INITIAL FINAL

PFE PFE

PFN PFN

CMN CMN

8. MICROWAVE LANDING SYSTEM DATA- ELEVATION

TX1 TX2 TX 1 TX2 MONITOR OT INITIAL FINAL OT INITIAL FINAL OT INITIAL FINAL OT INITIAL FINAL

Elevation Ei. Angle H. Ref Angle

PFE PFE H. Angle

PFN Ei. Angle L. Ref

CMN PFE L. Angle

OCI

BelowMGP Guidance

Usable Distance

• Remarks are required for fields marked with an asterisk

FAA Form 8240-16 (08-15) Supersed es Previous Edition PAGE 2 OF 3

9. MICROWAVE LANDING SYSTEM- COMMISSIONING DATA WORDS

f· FACILITY TYPE

~- MLS BASIC WORD 1 EXAMPLE

F DIS 200 MTR

AZ. PROP COV -40 TO +40 DEG

CLEARANCE SIGNAL TYPE SB

MLS BASIC WORD 2 EXAMPLE

MIN GLIDE PATH 3 .0 DEG

STATUS AZ. NORMAL

EL NORMAL

BZ OFF !TEST

DME FA. STD 1 AVAIL p. MLS BASIC WORD 3,4, & 6 EXAMPLE

AZ. BEAMWIDTH 3.0 DEG

EL BEAMWIDTH 2.0 DEG

DME DISTANCE 00 MTR

AZ. ZERO-DEG PLANE 173 DEG

BZ ZERO-DEG PLANE 353 DEG

GND EQU IP I DENT

E. MLSAUXAWORD1 EXAMPLE

AZ. ANTENNA OFFSET -89 MTR

AZ. TO DATUM PT DIST 6210 MTR

AZ. TO DATUM HEIGHT 0 MTR

AZ. ANT/RUNWAY ALIGN 0.00 DEG

AZ. ANT COORDINATE CONICAL/PLANAR

AZ. ANT HEIGHT 4 MTR F. MLSAUXAWORD2 EXAMPLE

EL ANTENNA OFFSET -91 MTR

THRESHOLD TO DATUM POINT 233 MTR

EL ANTENNA HEIGHT 5.5 MTR

DATUM POINT ELEVATION 387 MTR

THRESHOLD HEIGHT 0.7 MTR p. MLS AUXA WORD 3 EXAMPLE

DME OFFSET -89 MTR

DME TO DATUM POINT 0 MTR

DME ANTENNA HEIGHT 5 MTR

RUNWAY STOP END DIST 673 MTR

~- MLSMISC

CHANNEL/FREQ

DESIGNED PROCEDURAL AZIMUTH

DMECHANNEL

• Remarks are required for fields marked with an asterisk

FAA Form 8240-16 (08-15) Supersedes Prevkws Edition PAGE 3 OF 3

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-17

FLIGHT INSPECTION REPORT

RNAV

1. FLIGHT INSPECTION REPORT HEADER

I DENT STATE CTRY INSPECTION DATE(S) I II II II LOCATION RUNWAY CTRL NUMBER INSP TYPE I II II II

3. FACILITY INFORMATION

PROCEDURE TYPE RNP

PROCEDURE NAME WAAS HPL

PROC MODIFIED WAASVPL

SENSOR STATUS GEOSNR

ARINC 424 CODING FAS VERT. P.A. (Comm)

ADD. RUNWAYS FAS VERT. P.A. (Actual)

FRC TCH (Comm)

CRS ERROR TCH (Actual)

I I

5. REMARKS

6. FLIGHT INSPECTION DATA

2. CREW INFORMATION

PIC SIC MS A/C NO I I II liN/A II ACM FIFO I I II

PROCEDURE EVALUATION

HUMAN FACTORS

OBSTACLE VERI F.

COMMUNICATIONS

LIGHTING SYSTEMS

PROC FL YABILITY

A. (j} ROUTE· SID· STAR· DP G) SlAP B. DME FACILITIES SUPPORTING PROCEDURE

WAYPOINT NAME SAT/UNSAT

• Remarks are required for fields marked with an asterisk

I

I

FAA Form 8240-17 (08-15) Supersedes Previous Edition PAGE 1 OF 1

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-20

AVNIS Data Change Submission

1. TO: Flight Inspection Central Operations

FAX: (405) 954-3164 EMAIL: 9-AMC-AVN-AVN210-DATA

ATTENTION:

Please submit the following changes for incorporation into the appropriate flight publications.

LOCATION ID: TYPE

2. CANCEL: FACILITY RESTRICTION ("FROM" CW ''TO")

CMPNT DATE FROM TO BYD BELOW REMARKS

CHECKPOINT:

TYPE AIRPORT RAD DIST ALT DESCRIPTION

3. PUBLISH: FACILITY RESTRICTION ("FROM" CW "TO")

CMPNT DATE FROM TO BYD BELOW REMARKS

CHECKPOINT:

TYPE AIRPORT RAD DIST ALT DESCRIPTION

4. ROLLOUT/GS CBP:

A. R.O. CODE: C. ACTUAL CLASS: E. GS CBP CODE: -------- ------ ---------

B. TSS ASSIGNED CODE. D. PUBLISHED CLASS F. TSS VERIFICATION: ----- ---- -------

.G. UPGRADE NUMBER -------

5. REMARKS:

6. DATE O F INSPECTION: AIRCRAFT NO: DATE SENT: --------- ------- -----

PILOT: MISSION SPECIALIST:

AVNIS Data Change Submission

1. TO: Flight Inspection Central Operations

FAX: (405) 954-3164 EMAIL: 9-AMC-AVN-AVN210-DATA

ATTENTION: ---------------

Please submit the following changes for incorporation into the appropriate flight publications.

LOCATION … ID: … TYPE … _

2. DATA SHEET CHANGES:

3. DATE OF INSPECTION: AIRCRAFT NO: DATE SENT:

PILOT: MISSION SPECIALIST:

FLIGHT INSPECTION REPORT OBSTACLE EVALUATION

1. FLIGHT INSPECTION REPORT HEADER 2. CREW INFORMATION IDENT INSPECTION DATE(S) INSP TYPE PIC SIC MS AVC NO

ACM FIFO

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-21

3. OBSTACLE INFORMATION

IDENTIFICATION OF NEW CONTROLLING OBSTACLE LOCATION ESTIMATE OF HEIGHT PROCEDURE NAME DESCRIPTION LAT/LON or RADIAL/BEARING & DISTANCE MSL AGL

4. NOTAMs

5. REMARKS

FAA Form 8240-21 (08-15) Supersedes Previous Edition PAGE 1 OF 1

This Page Intentionally Left Blank

Appendix A. FAA Flight Inspection Report Forms › FAA Form 8240-23

I

I

FLIGHT INSPECTION REPORT

PRM/FMA

1. FLIGHT INSPECTION REPORT HEADER

I DENT STATE CTRY INSPECTION DATE(S) II II II LOCATION INSP TYPE II

1#i'3'''t''~'#•'AA&t+l''·'~

FACILITY STATUS

5. REMARKS

6. FLIGHT INSPECTION DATA

APPROACH DATA

RUNWAY/IDENT

MODES/CODES

TRANSPONDER CHECK

USABLE DISTANCE

RW Y INBOUND COURSE & NTZ WIDTH BOUND.

ALTITUDE BOUNDARY

VMD AND/OR NTZ BOUNDARY(IES)

APCH/I\IISSED APCH

LOW ALTITUDE COVERAGE

COMMUNICATIONS

APPROACH STATUS

2. CREW INFORMATION

PIC SIC MS NCNO I I II I II I ACM FIFO I I II I

* Remarks are required for fields marked with an asterisk

FAA Form 8240-23 (OB-15) Supersedes Previous Edition PAGE 1 0 F 2

FLIGHT INSPECTION REPORT

PRM/FMA

6. FLIGHT INSPECTION DATA

APPROACH DATA

RUNWAYIIDENT

MODES/CODES

TRANSPONDER CHECK

USABLE DISTANCE

RWY INBOUND COURSE & NTZ WIDTH BOUND.

ALTITUDE BOUNDARY

VMD AND/OR NTZ BOUNDARY(IES)

APCH/MISSED APCH

LOW ALTITUDE COVERAGE

COMMUNICATIONS

APPROACH STATUS

6. FLIGHT INSPECTION DATA

APPROACH DATA

RUNWAYIIDENT

MODES/CODES

TRANSPONDER CHECK

USABLE DISTANCE

RWY INBOUND COURSE & NTZ WIDTH BOUND.

ALTITUDE BOUNDARY

VMO AND/OR NTZ BOUNDARY(IES)

APCH/MISSED APCH

LOW ALTITUDE COVERAGE

COMMUNICATIONS

APPROACH STATUS

6. FLIGHT INSPECTION DATA

APPROACH DATA

RUNWAY/IDENT

MODES/CODES

TRANSPONDER CHECK

USABLE DISTANCE

RWY INBOUND COURSE & NTZ WIDTH BOUND.

ALTITUDE BOUNDARY

VMD AND/OR NTZ BOUNDARY(IES)

APCH/MISSED APCH

LOW ALTITUDE COVERAGE

COMMUNICATIONS

APPROACH STATUS

*Remarks are required for fields marked with an asterisk

FAA Form 8240-23 (08-15) Supersedes Previous Edition PAGE20F2

5. Remarks. › a. Receiver Checkpoints.

08/30/2015 8240.36N Appendix B

Appendix B. Rho-Theta Systems

FAA Form 8240-2

Use FAA Form 8240-2 to report Rho-Theta inspections and instrument flight procedures (IFPs) dependent primarily upon the rho-theta facility.

1. Flight Inspection Report Header. Complete in accordance with Chapter 3.

2. Crew Information. Complete in accordance with Chapter 3.

3. Facility Information.

a. VOR, TACAN, VOT, DME Coverage and DME Accuracy. For each applicable item, select either “Inspected” or “Required, Not Inspected*.” If an inspection was required, but not inspected, explain in the remarks. For VOT inspections, select “Inspected/ PIR” only if a PIR was used during inspection. For DME, specify the status of the inspection. If unsatisfactory, explain in the remarks.

b. Voice. Select “LIVE” and report the status of a live voice inspection. If not capable of broadcasting live voice, leave blank. Select the applicable recorded voice transmissions (i.e., ATIS, AWOS, HIWAS, TWEB, Other*) when the facility is supposed to broadcast the recording, and report the the status. If the system is not broadcasting a recording, but source documentation shows it is supposed to broadcast, select Unsat* and explain in the remarks. List applicable NOTAMs, in accordance with Chapter 3.

c. Standby Power and Ident. Select each item inspected and report the status.

d. Facility Type. Select the appropriate facility type, as determined by the AIRNAV datasheet.

e. Facility Status. Facility status classification is determined in accordance with FAA Order 8200.1, Chapter 5. Select the “as left” condition. Explain an “unusable” or “restricted” classification in the remarks, and include associated NOTAMs in Block 4.

f. SIAP(s) Verified. Complete in accordance with Chapter 3. Include an IFP statement in the remarks for new, changed or amended SIAPs.

4. NOTAM(s). Complete in accordance with Chapter 3.

5. Remarks. In addition to the remarks required in Chapter 3, clearly describe restrictions, unsatisfactory conditions, unusable facilities/ IFPs, and non-standard results. Use FAA Form 8240-1 “Continuation Sheet,” when additional space is required.

a. Receiver Checkpoints. When commissioning or reestablishing a receiver checkpoint or VOR Test Facility, describe in the remarks. For receiver checkpoints, include the type checkpoint, facility name (and airport name, when applicable), azimuth (degrees magnetic from

5. Remarks. › g. USAF VOR.

08/30/2015 8240.36N Appendix B

the facility), distance (tenths of a NM), altitude (airborne only), and description. For VOTs, include the facility name (and airport name), frequency, type facility, and description (if applicable).

Examples:

- Ground Checkpoint: Enid (Vance AFB); 143°; 0.8NM; On Runup Pad Rwy 35R

- Airborne Checkpoint: Will Rogers (Clarence E. Page Muni); 297°; 12.8NM; 2,900ft;

AER 35L

- Airborne Checkpoint: Midland; 224°; 11.0NM; 4,000ft; Over Odessa water tank

- VOT: Oklahoma City Rogers (Will Rogers World Airport); 108.8; Airborne and Ground;

Within 10NM radius between 3000’ and 5000’ VOT unusable east of Rwy 17L-35R.

- VOT: San Antonio International; 110.4; Ground

b. Radial Alignment. Include the remark, “Flight Inspection Services Technical Services Team authorized radial alignment in lieu of an alignment orbit.”

c. Reference Alignment. Indicate the date the crew notified maintenance of the ARR/ orbit reference alignment establishment/ re-establishment, (reference FAA Order 8200.1, Chapter 11).

d. Transmitter Changes During Alignment Orbit. Include the following remark, “Transmitter changes were accomplished during the alignment orbit IAW FAAO 8200.1, Paragraph 11.20f(1)(c), beginning with transmitter ___.”

e. VOT. When commissioning a VOT, indicate the identification feature (dots or a series of dots that cannot be interpreted as Morse code).

f. VOT Inspected Using a Portable ILS/ VOR Receiver (PIR).

(1) Record the PIR detected course deviation, modulation levels, and signal strength.

(2) Record the model, serial number, and calibration date of the PIR.

(3) Add the remark, “Flight Inspection Services Technical Standards Team authorized VOT flight inspection via PIR.”

(4) Do not add any data in Field 7C (Radial Data) of FAA Form 8240-2.

(5) Place an asterisk in the “Aircraft Number” field.

g. USAF VOR. Enter the modulation value(s) found on at least one radial or arc segment inspected. Report the values using the format modulations/ radial flown or arc/ start - stop radials/ distance(s) to the nearest mile/ MSL altitude divided by 100. Radial Example:

6. Flight Inspection Data. › b. Reference Radial/ Monitor.

08/30/2015 8240.36N Appendix B

AM=30.8, FM=16.4, 9960=29.5/312/16-12/37. Orbital Example: AM=30.9, FM=15.8, 9960=32.1/312 cw 349/40/25.

6. Flight Inspection Data. For a periodic with orbit inspection, report the orbital data in 6A. Do not enter a date in the “Ref Date” field for periodic data. Completion of both 6A and 6B is required when the reference radial and mean orbital alignment are established/ re-established. This block should also be completed when there is a need to permanently change flight profiles (e.g., direction, distance and /or altitude). The Data Specialist will transfer data from the flight inspection report to the AIRNAV datasheet whenever there is a date entered in the “Date Established” field.

Enter the azimuth monitor evaluation results when accomplished.

When an out-of-tolerance condition is found during an orbit, report Orbital Data (Block 8).

a. Orbital Data. Enter the mean alignment (e.g., + 0.2). Enter the maximum negative and the maximum positive alignment error (include the sign). FIRPS will automatically calculate and enter the “spread”.

Enter the orbit direction (CW or CCW) under the DIR field.

Enter the altitude divided by 100 in this block when the altitude is the same during the entire orbit. If altitude changes were required during the orbit, annotate in the remarks the different altitude(s) divided by 100 and the radial where the altitude change occurred (e.g., Altitude changed on alignment orbit 50/ 015-090, 60/ 091-135, etc.).

Enter the distance the alignment orbit was flown to the nearest tenth of a mile. If the orbit distance changed during the alignment orbit, annotate in the remarks the distance/radials where the distance changes occurred (Example: Distance changed on alignment orbit 9/ 015-090, 8/ 091-135).

b. Reference Radial/ Monitor. Select “VOR” or “VOT”. This field requires no ARR data, unless a new reference is accomplished or a monitor check is conducted. The ARR data will normally be in the Block 7 Radial Data block of the report.

(1) Reference Radial. For AFIS, enter the azimuth, the segment distance (to the nearest mile), and the altitude flown divided by 100 (Example: 270/ 20-15/ 45). When a Checkpoint is used, enter the azimuth and distance of the reference Checkpoint and the altitude flown divided by 100 (e.g., 265.5/ 18.3/ 45).

For VOT, enter the azimuth 360°/ from (e.g., 360/ from).

(2) Checkpoint. For VOR monitors evaluated while airborne, enter the location as detailed above for the Reference Radial. If monitors are checked where the Reference Radial/ Checkpoint was evaluated, enter "Same." If the monitors are established on the ground, enter the azimuth, distance, and the term "Gnd" (e.g., 041.1/6.7/Gnd). Describe the airport location in the remarks (carrying forward the airport location on subsequent reports is optional).

7. Radial Data. › b. Radial Use.

08/30/2015 8240.36N Appendix B

For VOT monitors, enter "VRP" if VOT Reference Point was used for monitor evaluation. If the “VRP” was not used, enter an asterisk and describe evaluation location in the remarks.

(3) TX, Alignment, Alarm +, Alarm -. Use the appropriate fields to report the results of the Reference Radial/ monitors.

(a) “TX”. Enter the transmitter evaluated. If a facility has two transmitters and both are checked, enter the transmitter number as shown in the Dual Transmitter example below.

(b) Enter the “normal condition” alignment error determined at the Reference Radial/ Checkpoint, or ARR if AFIS is used, in the Reference Radial “Alignment” column.

(c) When monitors are checked, enter the amount of shift. “Alarm +” is clockwise, AFIS code "R" and “Alarm -“ is counterclockwise, (AFIS code L) in the Checkpoint columns. The amount of shift must be referenced to the “normal condition” alignment error measured at the location the monitors are checked. The Checkpoint “Alignment” column will be left blank. See Examples 1 and 2.

Example 1. Single Transmitter

TX ALIGNMENT ALARM + ALARM -

Reference Radial 265.5/ 18.3/ 45 1 -0.4

Checkpoint Same 1 0.9 0.9

Example 2. Dual Transmitter

TX ALIGNMENT ALARM + ALARM ­

Reference Radial 270/ 20-15/ 45 1/ 2 -0.4/ -0.5

Checkpoint 042.0/ 6.7 nm/ GND 1/ 2 0.9/ 0.8 0.8/ 0.7

c. Date Established. Enter month, day, and year when the orbit/ reference radial alignment was established/ re-established for each facility/ component checked.

7. Radial Data.

a. Service Designation. Use the drop-down menu and select the appropriate facility.

b. Radial Use. Use the drop-down menu and select an appropriate abbreviation (see definitions below). Create a custom abbreviation if not present in the drop-down menu. If not obvious, explain custom abbreviations in the remarks. This field may be blank.

7. Radial Data. › g. Roughness/ Scalloping.

08/30/2015 8240.36N Appendix B

Radial Use Examples:

5DEG Offset (Special Check) of VOR APCH ACP Airborne Receiver Checkpoint APCH Approach ARR Automated Flight Inspection System (AFIS) Reference Radial DIR Direct Route FEDR Feeder GCP Ground Receiver Checkpoint IAPCH Initial Approach INTX Radial Used to Support a Fix or Intersection J___ Jet Route (e.g., J180) MAPCH Missed Approach NULL Null Radial REF Reference Radial RNAV Area Navigation (RNAV) Procedures SID Standard Instrument Departure STAR Standard Terminal Arrival Route V___ Victor Airway (e.g., V16) HOLD Holding Pattern COV Coverage Radial DP Departure Procedure ESV Expanded Service Volume

c. Azimuth. Enter the magnetic azimuth from the facility (in whole degrees). For RNAV procedures, enter the procedure start/ stop azimuth in tenths of degrees (e.g., 120.6 - 060.5). VOT azimuth is entered as "360/ from."

d. Transmitter(s). Identify which transmitter was inspected. If both transmitters were alternated during a single check, enter the transmitter with the greatest alignment error first, (e.g., 2/ 1 with TX 2 having the greatest error).

e. MSL Altitude. Enter the altitude divided by 100 (e.g., "20" for 2,000 feet, "7.2" for 720 feet). If altitude changes occurred, enter the highest and lowest altitudes in the order checked (e.g., 20/ 7.2). Leave blank when reporting ground Checkpoints.

f. Distance From/ To. Show the starting point (From) and the termination point (To) in nautical miles from the facility.

g. Roughness/ Scalloping. For in-tolerance parameters, enter the maximum amplitude to the nearest tenth of a degree and indicate the distance from the station (e.g., 2.2/ 16.0).

7. Radial Data. › m. Signal Strength.

08/30/2015 8240.36N Appendix B

For Out-of-tolerance (OT) parameters, enter the amplitude and distance closest to the facility. When reporting OT roughness/ scalloping that meets acceptable aggregate criteria, report the worst case of roughness/ scalloping, the mileage where it occurred, and place an asterisk in the reporting field, e.g., *5.0°/ 25.5. In the remarks, place a corresponding asterisk and state "Order 8200.1, Paragraph 11.60a (VOR) or 11.60b (TACAN) applied." If an OT parameter occurs multiple times on one radial in separate segments, enter each additional segment in the remarks block.

For RNAV procedures, report maximum roughness/ scalloping and azimuth (e.g., 1.5/ 010).

h. Bends/ CMA and Bends. For in tolerance parameters, enter the maximum Bend and Bend/ CMA amplitude to nearest tenth of a degree. Indicate the direction of the bend as “+” or “­ “ value, and the distance from the facility where it occurs (e.g., + 1.2/ 15.6).

For Out-of-tolerance (OT) paramenters, enter the OT amplitude and distance closest to the facility. (See above subparagraph when entering multiple OT conditions.)

i. Polarization. Enter “SAT” or “UNSAT.” Describe unsatisfactory conditions in the remarks.

j. Alignment Error. Enter the alignment error, as a "+" or "-" value, and the distance from the facility at which it occurs.

If AFIS average alignment is reported, indicate the alignment and the start-stop distance from the facility thoughout the entire area that was sampled (e.g., + 0.5/ 10.2-65.5).

Visual references used in evaluating radial alignment to runway thresholds or airport environments will be reported as “SAT” or “UNSAT.”

When an RNAV procedure is evaluated using AFIS orbital techniques, enter the average orbit alignment error and start-stop radials of measured arc.

k. Modulations. Enter "SAT" or "UNSAT." For USAF VOR facilities, list the modulation value(s) in the remarks, in accordance with paragraph 5.g. above.

l. Transmitter Difference. Enter the alignment difference between transmitters, to the nearest tenth of a degree.

m. Signal Strength. For VOR signal strength in microvolts, enter the actual value. For OT levels, enter value with asterisk (e.g., 4*). In the remarks, enter the distance where the OT level occurred. Signal strength exceeding 300 µV may be reported as 300+.

Report TACAN signal strength as Satisfactory “SAT”. For Unsatisfactory TACAN signal strength, enter “UNSAT*” and the distance nearest the facility it occurred (e.g., UNSAT*/ 25). Enter in the remarks, “* Maintenance briefed … (date).”

8. Orbital Data. › h. TACAN Coverage-Signal Strength.

08/30/2015 8240.36N Appendix B

n. Interference. Enter "SAT" if no interference is observed; enter "UNSAT*" if interference occurs and document the area of interference in the remarks.

8. Orbital Data.

a. Transmitter Number (No). Select the appropriate transmitter for VOR and the appropriate transponder for TACAN.

b. DME Distance Unlock. Select the check box when there are unlocks and list the azimuth at which they occur (e.g., 012-023, 350-001) in Block 8B.

c. TACAN Azimuth Unlock. Select the check box when there are unlocks and list the azimuth from the facility for the area where unlocks occur (e.g., 012-023, 350-001).

d. Area of interference. Select the check box when there is an area of interference observed to have a detrimental effect on the usability of the facility. List the azimuth from the facility for the area the interference is observed (e.g., 012-023, 350-001).

e. VOR Azimuth exceeds 2.5°. When radial displacement exceeds ± 2.5°, enter the maximum course displacement and azimuth of occurrence in the appropriate block. Each block represents a 10° segment of the orbit. In the “00” block, an entry of azimuth misalignment from 000 - 009 may be recorded (e.g., 2.6/ 006) and in the “10”block, azimuth misalignment from 010 - 019 may be recorded (e.g., 2.8/ 017).

f. TACAN Azimuth exceeds 2.5°. When a radial displacement exceeds ±2.5º, enter the maximum course displacement and azimuth of occurrence in the appropriate field. Each field represents a 10° segment of the orbit. In the “00” field, an entry of azimuth misalignment from 000 - 009 may be recorded (e.g., 2.6/ 006) and in the “10” field, azimuth misalignment from 010 - 019º may be recorded (e.g., 2.8/ 017).

g. VOR Coverage – Signal Strength. Document levels below -93 dbm or 5 µV. If the VOR signal strength drops below -93 dbm or 5 µV, enter the lowest value in the appropriate field. Each field represents a 10º segment of the orbit. In the “00” field, SS below 5 µV between radials 000 – 009 may be recorded (e.g., 3/ 006) and in the “10” field, SS below 5 µV between radials 010 - 019º may be recorded (e.g., 4/ 017).

h. TACAN Coverage-Signal Strength. Document where the TACAN or DME (U.S. Navy shipboard TACAN) signal strength drops to a level causing an Azimuth or DME unlock. Enter data in the appropriate field using the example in the previous paragraph.

08/30/2015 8240.36N Appendix B

This Page Intentionally Left Blank

Appendix C. Ground-Based Augmentation Systems (GBAS) › 5. Remarks.

08/30/2015 8240.36N Appendix C

Appendix C. Ground-Based Augmentation Systems (GBAS)

FAA Form 8240-4

Use FAA Form 8240-4 to report ground-based augmentation system commissioning, periodic, and special inspections. Multiple GBAS facilities may be installed at a single location. Therefore, use separate forms for each GBAS facility inspected.

1. Flight Inspection Report Header. Complete in accordance with Chapter 3.

2. Crew Information. Complete in accordance with Chapter 3.

3. GBAS Coverage

a. Profile. Select drop-down box and enter direction of flight, “CW” for clockwise or “CCW for counter clockwise.

b. Altitude. Enter minimum altitude flown, divided by 100 (e.g. “20” for, 2,000 feet, “7.2” for 720 feet.). If altitude changes occurred, enter the highest and lowest altitudes in the order checked (e.g., 20/ 7.2).

c. Radius. For orbital assessments enter distance in “nm” nautical miles from the reference point on the field. Reference point will be the LAT/ LONG coordinates of the GBAS.

d. Signal Strength. Enter the minimum field strength in dB(s).

e. Dmax NM. For facilities broadcasting Dmax, enter the Maximum Use Distance as defined by the GBAS Facility (e.g., 22.7). If positive course guidance and data continuity cannot be maintained to the Dmax distance, the facility must be restricted.

f. GBAS Frequency. Enter the GBAS Frequency.

g. Polarization. Select the drop-down box and enter the type of polarization associated with the GBAS.

h. SIAP(s) Verified. Complete in accordance with Chapter 3. Include an IFP statement in the remarks for new, changed or amended SIAP.

i. Facility Status. Facility status classification is determined in accordance with FAA Order 8200.1, Chapter 5. Select the “as left” condition. Explain an “unusable” or “restricted” classification in the remarks, and include associated NOTAMs in Block 4.

4. NOTAM(s). Complete in accordance with Chapter 3.

5. Remarks. For commissioning type inspections, if the facility is not FAA owned, enter a remark stating the owner. Use plain language when explaining flight inspection results, restrictions, unsatisfactory conditions, unusable facilities or IFPs, and any other condition

08/30/2015 8240.36N Appendix C

6. Flight Inspection Data. › b. Final Approach Segment (FAS) Data.

necessitating comments. Use FAA Form 8240-1 “Continuation Sheet,” if necessary. Reference Chapter 3 for additional remarks guidance.

6. Flight Inspection Data.

a. VHF Data Broadcast (VDB) Coverage Assessment. Enter the VDB Coverage information.

(1) Runway. For an approach, enter the runway served by the procedure.

(2) Airport ID. Enter the airport identification listed in the SIAP information for each approach procedure.

(3) Lower Limit. Select drop-down box and enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in the remarks.

(4) Upper Limit. Select drop-down box and enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in the remarks.

(5) Left Limit. Select drop-down box and enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in the remarks.

(6) Right Limit. Select drop-down box and enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in the remarks.

(7) Missed. Select drop-down box and enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in the remarks.

(8) Rollout. Select drop-down box and enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in the remarks.

(9) CVG MVA (Coverage from Minimum Vector Altitude). Select drop-down box and enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in the remarks.

(10) CVG USV (Coverage from Upper Service Volume). Select drop-down box and enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in the remarks.

b. Final Approach Segment (FAS) Data. Enter the FAS Data information

(1) Runway. For an approach, enter the runway served by the procedure.

(2) Airport ID. Enter the airport identification listed in the SIAP information for each approach procedure.

(3) CRC. Enter the exact CRC remainder as indicated on FAA Form 8260-10 or equivalent.

Appendix C. Ground-Based Augmentation Systems (GBAS) › 7. Additional Pages.

08/30/2015 8240.36N Appendix C

(4) Channel. Enter the assigned Channel number for each SIAP.

(5) RPI (Reference Path Identifier) Enter the broadcast Morse code RPI for each SIAP (e.g., G22B).

(6) Course Alignment. Enter the actual course error (e.g., L00.01).

(7) Glide Path. Enter the proposed commissioned vertical path angle and the actual vertical path angle for the GBAS final approach segment (e.g., 3.00/ 3.02).

(8) TCH. Enter the procedurally calculated TCH and the actual derived TCH for the GBAS final approach segment in tenths of feet (e.g., 55.0/ 54.7).

7. Additional Pages. Use FAA Form 8240-4-3 to add additional VDB coverage assessment and FAS data information. Use FAA Form 8240-4-4 if additional remark information is needed.

08/30/2015 8240.36N Appendix C

This Page Intentionally Left Blank

Appendix D. NDB, DF, Lights, and Communications › 5. Remarks.

08/30/2015 8240.36N Appendix D

Appendix D. NDB, DF, Lights, and Communications

FAA Form 8240-5

Use FAA Form 8240-5 to report NDB, DF, Lighting, or Communication system, and associated instrument flight procedure inspections. Report bearings as “FROM” the facility, unless there is a specific requirement necessitating reporting “TO” the facility.

If an NDB facility is scheduled for inspection, or an NDB facility discrepancy is discovered, report the inspection results on this form. However, if an NDB is used solely as a Compass Locator or supporting NAVAID to an ILS or LOC procedure, and does not support an NDB approach or airway, report in conjunction with the ILS inspection, using the “Compass Locator” fields on the ILS report. With the exception of VGSI systems, when a lighting system discrepancy is discovered during a NAVAID or SIAP inspection, report the discrepancy on the form associated with the NAVAID or SIAP. Report VGSI discrepancies using this form, or when specifically tasked to inspect a lighting system.

NOTE: The “Lighting System” field (on some forms) is used to report the status of already-commissioned lighting systems supporting reduced visibility minima. These systems include Approach Lighting Systems (ALS), High Intensity Runway Lights (HIRL), Touchdown Zone Lights (TDZL), and Runway Centerline Lights (CL).

1. Flight Inspection Report Header. Complete in accordance with Chapter 3.

2. Crew Information. Complete in accordance with Chapter 3.

3. Facility Information. Indicate the “as left” status of the inspected facility/component(s) (i.e., DF, Comm, Vis Aid, NDB, NDB/DME) matching the IDENT on the form. Use the dropdown menu and select the appropriate entry. If required, but not inspected, add a remark and explain in the remarks. Leave blank if not required and not inspected.

a. Facility Status. Facility status classification is determined in accordance with FAA Order 8200.1, Chapter 5. Select the “as left” condition. Explain an “unusable” or “restricted” classification in the remarks, and include associated NOTAMs in Block 4. For Communications inspections, leave blank. For VGSI system inspections (i.e., VASI, PAPI, etc.), always assign a status. With the exception of VGSI systems, lighting system discrepancies do not necessarily result in a restriction. Should a hazard to safety exist, classify the lighting system “unusable.” When changing a previously “unusable” lighting system to either “unrestricted” or “restricted,” include a remark explaining the reason for the change.

b. SIAP(s) Verified. Complete in accordance with Chapter 3. Include an IFP statement in the remarks for new, changed or amended SIAPs.

4. NOTAM(s). Complete in accordance with Chapter 3. If the NDB is associated with an ILS, any restriction to the NDB must be added to the ILS AIRNAV datasheet.

5. Remarks. Complete in accordance with Chapter 3.

Continue reading ↓ 120 of 224 passages shown