Order 8240.36L Instructions for Flight Inspection Reporting
This document is cancelled. It may have been replaced. Check the official source before relying on it.
Text read by OCR from a scanned file (5 of 126 pages). Check the original, as some words may be misread.
Cover
Distribution: Special Addressees Initiated By: Aviation System Standards Flight Inspection Policy
ORDER
8240.36L
FLIGHT INSPECTION REPORT PROCESSING SYSTEM
(FIRPS)
October 1, 2006
DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
RECORD OF CHANGES DIRECTIVE NO. 8240.36L
Record of Changes
CHANGE SUPPLEMENTS OPTIONAL CHANGE SUPPLEMENTS OPTIONAL TO BASIC
TO BASIC
Distribution: Initiated By: Air Traffic Technical Operations (ATO-W) ATO-W Service Areas; NAS Implementation Centers; Aviation System Standards Flight Inspection Operations Offices & Crewmembers; Flight Inspection Operations Group Special Military Addressees Flight Inspection Policy Team (AJW-3310)
Signature Page
Effective Date:
10/01/06 SUBJ: Flight Inspection Report Processing System (FIRPS) This order provides policy, guidance, and distribution requirements for flight inspection reports and records when using the electronic Flight Inspection Report Processing System (FIRPS). Flight inspection files (e.g., flight inspection reports, data sheets, oscillographic recordings, electronic media, photographs, correspondence) are federal records. Unless classified by specific authority, they are available, on request, to the public by the authority of the Freedom of Information Act, Title 5, United States Code, Section 552. The policy and legal requirements for records management are contained in other Federal Aviation Administration (FAA) orders. Guidelines for record disposition are contained in FAA Order 1350.15, Records Organization, Transfer, and Destruction Standards. /s/ Thomas C. Accardi Director of Aviation System Standards
U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
ORDER
8240.36L
This Page Intentionally Left Balnk
Table of Contents
10/01/06 8240.36L
Page iii
TABLE OF CONTENTS Page # CHAPTER 1. INTRODUCTION 1. Purpose … 1 2. Distribution … 1 3. Effective Date … 1 4. Cancellations … 1 5. Explanation of Changes … 1 6. Computer Generated Forms … 4 7. Definitions, Acronyms, and Abbreviations … 5 8. Information Currency … 6 9 – 10 Reserved … 6 CHAPTER 2. GENERAL INFORMATION 11. General Forms Completion … 7 12. Common Report Data … 9 13. Corrected Copies of Reports … 14 14. Security Classification of Flight Inspection Reports … 14 15. Distribution of Reports and Recordings … 15 16 – 20 Reserved … 17 CHAPTER 3. REQUIRED REPORT REMARKS 21. Remarks Field … 18 22 – 25 Reserved … 23 APPENDIX 1. Flight Inspection Forms … A1-1 Flight Inspection Report – Continuation Sheet, FAA Form 8240-1 … A1-3 APPENDIX 2. Flight Inspection Report – VOR, VOR/ DME, VORTAC, TACAN, VOT … A2-1 FAA Form 8240-2 … A2-9 APPENDICES 3 - 4 (Reserved) APPENDIX 5. Flight Inspection Report – Non-Directional Beacon, Direction Finding, Visual Aids, Communications … A5-1 FAA Form8240-5 … A5-7 APPENDIX 6. Flight Inspection Report – Precision Approach Radar , GPN-22/ TPN-25 Continuation Sheet, PAR TPN-22 Continuation Sheet … A6-1 PAR, FAA Form 8240-6 … A6-5 PAR GPN-22/ TPN-25 Continuation Sheet … A6-6 PAR TPN-22 Continuation Sheet … A6-7
8240.36L 10/01/06
Page iv
TABLE OF CONTENTS
continued Page # APPENDIX 7. Flight Inspection Report – ILS Worksheet and ILS Continuation Worksheet … A7-1 ILS Worksheet, FAA Form 8240-7 … A7-5 ILS Continuation Worksheet, FAA Form 8240-7-1 … A7-6 APPENDIX 8. Flight Inspection Report – Instrument Landing System (ILS) … A8-1 FAA Form 8240-8 … A8-14 APPENDICES 9 - 10 (Reserved) APPENDIX 11. Flight Inspection Report – ILS/ MLS Maintenance Alert … A11-1 FAA Form 8240-11 … A11-2 APPENDIX 12. Flight Inspection Report – Surveillance Radar … A12-1 FAA Form 8240-12 … A12-5 APPENDIX 13. Flight Inspection Report – General Characteristics … A13-1 FAA Form 8240-13 … A13-3 APPENDIX 14. Flight Inspection Report – After Accident Continuation Sheet … A14-1 FAA Form 8240-14 … A14-4 APPENDIX 15. (Reserved) APPENDIX 16. Flight Inspection Report – Microwave Landing System (MLS) and MLS Commissioning Data Words … A16-1 FAA Form 8240-16 … A16-6 APPENDIX 17. Flight Inspection Report – Area Navigation (RNAV) … A17-1 FAA Form 8240-17 … A17-5 APPENDICES 18 - 20 (Reserved) APPENDIX 21. Flight Inspection Report – Controlling Obstacle Evaluation … A21-1 FAA Form 8240-21 … A21-2
Chapter 1 - Intro/ Explanation of Changes
10/01/06 8240.36L
Chap 1 Page 1 Par 1
CHAPTER 1. INTRODUCTION 1. PURPOSE. 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. DISTRIBUTION. This order is distributed to the Air Traffic Technical Operations Eastern, Central, and Western Service Areas; to the NAS Implementation Centers; to Flight Inspection Operations Offices and crewmembers in Aviation System Standards; and to special military addressees. 3. EFFECTIVE DATE. This order is effective October 1, 2006. 4. CANCELLATIONS:
a. FAA Order 8240.36K, Instructions for Flight Inspection Reporting, dated October 1, 2005.
b. FIRPS Test and Implementation Guidance with Changes 1 – 4.
c. Notice N VN200 8200.19, Flight Inspection Report Processing (FIRPS) Test and Implementation Guidance and Changes to FAA Order 8240.36, Instructions for Flight Inspection Reporting, dated July 18, 2005. 5. EXPLANATION OF CHANGES:
a. Chapter 1, Paragraph 6a. Clarified implementation paragraph.
b. Chapter 1, Paragraph 8. Clarified information currency instructions.
c. Chapter 2:
(1) Paragraph 11j. Added option to use “S” or “U” for report entry in addition to “SAT” and “UNSAT”.
(2) Paragraph 11k. Added guidance for AVNIS Data Change Submission.
(3) Paragraph 11l. Added guidance for PRM reporting requirements
(4) Paragraph 11m. Added guidance for procedure inspections.
(5) Paragraph 12i. Clarified “Inspection Type” requirements.
(6) Paragraph 12j(2). Clarified requirements.
(7) Paragraph 13. Updated organizational names.
(8) Paragraph 14d. Updated organizational names.
(9) Paragraph 15a(1). Changed requirement from “Name of crewmembers” to “Crew number”.
(10) Paragraph 15a(4). Changed specific mailing requirements to generic mailing instructions.
8240.36L 10/01/06
Page 2 Chap 1 Par 5
(11) Paragraph 15a(5). Changed shipping notification email address.
(12) Paragraph 15a(6). Added shipping address for Federal express.
(13) Paragraph 15b. Clarified after accident distribution procedures.
(14) Paragraph 15c. Clarified requirements and updated organizational names.
(15) Paragraph 15d. Clarified requirements and updated organizational names.
(16) Paragraph 15e. Updated organizational names.
(17) Paragraph 15f. Clarified reporting requirements for radio frequency interference.
(18) Paragraph 15h(2). Guidance added due to elimination of Appendix 23.
d. Chapter 3:
(1) Paragraph 21a(1). Clarified “Out of Tolerance Condition” requirements.
(2) Paragraph 21b. Clarified narrative requirements.
(3) Paragraph 21c. Clarified requirements.
(4) Paragraph 21d. Updated organizational name for reporting NOTAM(s).
(5) Paragraph 21g. Clarified reporting requirements for SIAP(s).
(6) Paragraph 21j. Added examples for reporting ESV(s) and clarified instructions.
(7) Paragraph 21r. Updated organizational names.
(8) Paragraph 21u. Added 1800 RVR reporting requirements.
e. Appendix 1. Updated FAA Form 8240-6, Precision Approach Radar and deleted FAA Forms 8240-20 and FAA 8240-22, which have been moved to the Aeronautical Data Management order.
f. Appendix 2:
(1) Paragraph a. Field 1. Flight Inspection Report Header. Condensed reporting instructions.
(2) Paragraph c. Clarified VOR/ PIR reporting instructions.
(3) Paragraph d. Corrected chapter and paragraph reference.
(4) Paragraph e. Field 5. Remarks. Added VOT description.
(5) Paragraph e(4). Corrected reference.
(6) Paragraph e(5). Made recording the model, serial number, and calibration date of the PIR a requirement (no longer optional).
(7) Paragraph f(2). Added clarification about when to enter ARR data.
10/01/06 8240.36L
Chap 1 Page 3 Par 5
(8) Paragraph g(2). Added “radial use selection” of “COV’ (Coverage radial).
(9) Paragraph g(6). Clarified reporting guidance.
g. Appendix 5:
(1) Paragraph a. Field 1. Flight Inspection Report Header. Condensed reporting instructions.
(2) Paragraph 3f. Facility Status. Clarified completion requirement when checking communication.
(3) Paragraph 6b(8). Clarified bearing error reporting requirement.
h. Appendix 6. FAA Form 8240-6, Pages 1, 2 and 3. The forms and the guidance have been rearranged and expanded to provide a user friendly, functional format.
i. Appendix 7. Added this appendix and guidance.
j. Appendix 8:
(1) Paragraph a. Field 1. Flight Inspection Report Header. Condensed reporting instructions.
(2) Paragraph 3r. Updated organizational names.
(3) Paragraph 3r(2). Added note.
(4) Paragraph 5c. Deleted term LCA and replaced it with “an altitude”.
(5) Paragraph 6i. Corrected reference subparagraph from “8j” to “6h”.
(6) Paragraph 6k. Added guidance for clarification.
(7) Paragraph 9f, 9g, 9i, and 9j. Corrected reference subparagraphs from “8j” to “6h”.
(8) Paragraph 10a., Field A. Changed field name to “Antenna Dephase”.
(9) Paragraph 10p(1). Added requirement to enter ARDH value in hundredths of feet.
(10) Paragraph 10p(3). Added requirement to enter RDH value in hundredths of feet.
(11) Paragraph 10r(3). Clarified guidance.
k. Appendix 12:
(1) Paragraph a. Field 1. Flight Inspection Report Header. Condensed reporting instructions.
(2) Paragraph 6d(1). Changed method to identify the airport where the surveillance approach terminates.
8240.36L 10/01/06
Page 4 Chap 1 Par 5
l. Appendix 13:
(1) Introduction Paragraph. Clarified when to use this form.
(2) Paragraph 1. Flight Inspection Report Header. Condensed reporting instructions.
(3) Paragraph 3. Clarified reporting requirements.
m. Appendix 14, Paragraph 3. Updated organizational names and special reports review guidance.
n. Appendix 16:
(1) Paragraph 1. Field 1. Flight Inspection Report Header. Condensed reporting instructions.
(2) Paragraph 5a, 6b(1), and 6b(12). Added definition of acronyms.
o. Appendix 17:
(1) Paragraph a. Field 1. Flight Inspection Report Header. Condensed reporting instructions.
(2) Paragraph 3(d). Changed field name from “RAIM” to “Sensor Status”.
(3) Paragraph 5. Added definition of acroyms.
p. Appendix 20. This appendix is removed from FAA Order 8240.36 and will be located in the Aeronautical Data Management order.
q. Appendix 22. This appendix is removed from FAA Order 8240.36 and will be located in the Aeronautical Data Management order.
r. Appendix 23. Deleted. This appendix is not needed since the source for mailing flight inspection reports is the database within the TSS Flight Inspection Records Team, AJW-335A. 6. COMPUTER GENERATED FORMS. This paragraph provides information on the automation of the flight inspection forms.
a. Implementation. This automated system will expedite filling out flight inspection forms and reduce the number of errors due to manual entries. This system also allows information to be extracted from sources such as text files and other databases.
b. Use of Automated Forms. The software package will provide an automated method for completing flight inspection forms. This automated process allows each user to fill in forms completely, accurately, and to print the forms.
10/01/06 8240.36L
Chap 1 Page 5 Par 6
c. Equipment Requirements. Each user office must have access to the appropriate hardware/ software package. The required software, as well as a user’s guide for the current form software package, may be obtained from the Information Technology Staff.
d. System Description. This electronic form processor has a visual interface and allows each user to work with forms using windows, pictures, and menus on a screen. The completed screen data and form may be printed on bond paper.
e. Some Features of the System. This program allows the user to:
(1) Bring a copy of the form into the work area on a screen.
(2) Tab or select particular fields on the forms with a mouse and type in required data.
(3) Automatically fill in areas on the form by the computer using many designated fields that contain relatively constant facility data.
(4) Fill in forms completely and accurately with many automatic checks and entries.
(5) Fill forms with information from central databases.
(6) Print forms efficiently.
f. Appendix 1, Flight Inspection Forms, contains a listing of forms used in reporting various facilities and types of inspections. 7. DEFINITIONS, ACRONYMS, AND ABBREVIATIONS. (Refer to Order 8200.1, United States Standard Flight Inspection Manual, for definitions, acronyms, and abbreviations.) This order contains instructions and guidance material. Directive verbs are used. In this order, the words:
a. Must in the second or third person means that an action is mandatory. "Must not" means that an action is prohibited.
b. Will indicates it is understood that an action is to be taken. Do not use "will" when you mean "must."
c. Should means that an action is desirable but not mandatory or, "We would like you to do it, but you don't have to."
d. May means an action is permissive - or "If you want to, go ahead."
8240.36L 10/01/06
Page 6 Chap 2 Par 8
8. INFORMATION CURRENCY. Comments regarding corrections, clarification, or suggested improvements regarding the content of this order should be forwarded to the Flight Inspection Policy Team, AJW-3310, for consideration. Your assistance is welcome. If an interpretation is urgently needed, you may call the Flight Inspection Policy Team, FTS 405 954- 3766, for guidance, but you should also use FAA Form 1320-19, Directive Feedback Information, as a follow-up to verbal conversation. 9 - 10. RESERVED.
Chapter 2 - General Info
10/01/06 8240.36L
Chap 2 Page 7 Par 11
CHAPTER 2. GENERAL INFORMATION 11. GENERAL FORMS COMPLETION
a. Reports. The flight inspector is responsible for initiating reports for all flight inspections.
b. Reporting Numeric Data. Unless otherwise stated, report numerical data to the following accuracy:
(1) Microamperes - To the nearest whole microampere.
(2) Altitude - To the nearest foot, mean sea level (MSL).
(3) Azimuth - To the nearest tenth of a degree.
(4) Percent - To the nearest tenth of a percent.
(5) Mileage - To the nearest tenth of a nautical mile.
(6) Angles - To the nearest hundredth of a degree.
(7) Widths - To the nearest hundredth of a degree.
(8) Latitude – Degrees, minutes, seconds, and hundredths of a second (north/ south).
(9) Longitude – Degrees, minutes, seconds, and hundredths of a second (east/ west).
NOTE: In accordance with FAA Order 8200.1, Formulas, the following guidelines must be used in rounding off computations. Measurements and calculations should be carried to one decimal place more than that required for tolerance application. Then apply the following criteria to round off a measurement.
Numerals 1 to 5, round off to zero.
Numerals 6 to 9, round off to the next higher value.
Example: Glidepath Course Width: 0.755° = 0.75°
0.756° = 0.76°
Exception: If a measurement exceeds a tolerance, it must not be rounded off to an in tolerance condition.
Example: Glidepath Course Width - 0.903° is out of tolerance.
8240.36L 10/01/06
Page 8 Chap 2 Par 11
c. Primary and Supplementary Report Forms. The current software for automated form completion must be used. The forms may be filled out by hand only when an interim report is required. Use black ink for data entry.
d. Non-Applicable Portions of Report Forms. If any part of a report form does not apply to the facility inspected or the type inspection conducted, leave it blank.
e. Type Inspection. Except for the special checks which meet periodic requirements, IAW Chapter 3, Paragraph 21o, report only one type of inspection per report form (i.e., if a periodic inspection is conducted on one component of a facility concurrently with a commissioning check of another component of the same facility, submit a separate report on each).
f. Facilities Supporting Other NAVAID(s). When a facility's primary purpose is to support a procedure on another NAVAID (e.g., 75 MHz marker beacon, DME, etc.), the supporting facility must be reported on the "NAVAID(s)" report form, unless otherwise directed in the appropriate appendix. If the facility component is a compass locator and supports a separate NDB approach procedure, refer to Appendix 5.
g. Surveillance Inspection Discrepancies. Report discrepancies of services and airport conditions on FAA Form 8240-13, Flight Inspection Report--General Characteristics. Report facility discrepancies found during a surveillance inspection on the appropriate facility report form (e.g., ILS, VOR, etc.).
h. Facility Performance. The report must reflect the facility "as left," unless specified otherwise by reporting instructions for a given facility type.
i. Satisfactory/ Unsatisfactory Report Entries. Unless otherwise stated in this order, enter "SAT" or “S” if satisfactory; enter "UNSAT" or “U” if unsatisfactory and refer to Chapter 3, Paragraph 21a.
j. AVNIS Data Change Submission. FAA Form 8240-20, AVNIS Data Change Submission, is provided within FIRPS. The completion requirements are identified in the Aeronautical Data Management order.
k. Precision Runway Monitor (PRM)/ Final Monitor Aid (FMA) Inspections. FAA Form 8240-5-4 is provided within FIRPS. The completion requirements are identified in FAA Order 8200.39.
l. Procedure Inspections. Report SID(s), STAR(s), and SIAP(s) on the form designated for the primary NAVAID of the procedure (e.g., an ASR approach is reported on FAA Form 8240-12, Surveillance Radar; a departure requiring interception of a radial is reported on FAA Form 8240-2, VOR, VOR/ DME, VORTAC, TACAN, VOT). Textual departure procedures not requiring the use of any NAVAID are reported on FAA Form 8240-13, General Characteristics. If procedural changes do not require recorded data, (e.g., MDA raised, controlling obstacle changed with no change in minima, or fixes within the FISSV) include the statement, “No electronic data required.”
10/01/06 8240.36L
Chap 2 Page 9 Par 12
12. COMMON REPORT DATA. Any additional information or exceptions to the following instructions are specified in the reporting instructions for each type facility. Instructions for reporting common information are as follow:
a. Common Data on Each Report Page. Page Number, Location, Ident, and Date must be included on all pages of a flight inspection report. This data may be autofilled.
b. State. Enter the state code for facilities located in the United States. Click on the drop-down box and select the appropriate entry.
c. Country. Enter the country code for facilities located outside the United States. Enter “US” for facilities located in the United States. Click on the drop-down box and select the appropriate entry.
d. Identifier (Ident) Field. Enter the facility IDENT listed on the Aviation System Standards Integrated Services (AVNIS) Facility Data Sheet, except:
(1) If the procedure is to a point in space, not a designated airport, enter the airport identifier assigned by the National Flight Data Center (NFDC). If no ident is assigned, leave blank.
(2) For a stand-alone point-in-space fix, enter the ARTCC identifier without a “K” prefix (e.g., ZSE).
(3) For routes, enter route name, i.e., Q501, etc.
(4) For a DP or STAR, enter the computer code listed on the PC form, i.e., computer code IDALE2.IDALE, enter “IDALE2”.
(5) If the facility identifier is changed, refer to Chapter 3, Paragraph 21.
(6) If mobile/ tactical facilities are installed for extended periods of time and utilized for instrument flight rules (IFR), the identification (ID) will be assigned the same as a permanent facility. If the facility is installed in support of a specific temporary (normally not to exceed 90 days) requirement, enter the four-letter ID as indicated in Chapter 3, Paragraph 21m.
8240.36L 10/01/06
Page 10 Chap 2 Par 12e
e. Owner Field. Enter the owner code listed in AVNIS. Acceptable codes are:
OWNER CODE DESCRIPTION A Air Force B Public C Coast Guard E FAA F&E Projects F FAA (Other than F&E) H International Public I International (Generic) J International Private K International Air Force L International Army M International Navy N Navy O Other (Specify in Remarks) P Private R Army S State X Public Special
NOTE: If ownership should change, refer to Chapter 3, Paragraph 21.
(1) International: Facilities/ approaches/ procedures owned by the foreign government shown in the location field.
(2) Private: Facilities/ approaches/ procedures owned by non-governmental interests. This owner is not always indicated in the location field. For commissioning reports only, identify the specific owner (actual corporation or organization) in the “Remarks” section.
(3) State, County, or Municipality: Facilities/ approaches/ procedures owned by a domestic governmental interest other than the Federal Government. For commissioning report only, identify the specific owner in the “Remarks” section.
(4) Other: Facilities owned by the Federal Government other than FAA, such as U. S. Trust Territory, NASA, U. S. State Department. Indicate in the “Remarks” section the actual owning interest.
f. Region Field. The region designator must be the authorized 3-letter code for the FAA region in which the reported facility/ approach/ procedure is located. For military-owned facilities and foreign governments, leave blank.
10/01/06 8240.36L
Chap 2 Page 11 Par 12g
g. Date(s) of Inspection Field. Record the UTC date(s) of flight inspection as follows:
(1) Inspection started and completed in one day: 2/1/88
(2) Inspection conducted over consecutive days: 1/12-15/89
(3) Inspection conducted over several nonconsecutive days: 8/6, 8, 10/89
(4) Combined inspections: 10/16, 19-21/89.
h. Location Field. Facility location information will be obtained from the AVNIS Facility Data Sheet (do not enter airport name). For shipboard tactical air navigation (TACAN), enter the name of the ship and the hull number (e.g., USS Nimitz - CVN68). For point in space procedures, enter the airport name (if specified), city, and state as identified on the PC form. For a stand-alone point in space fix, enter the waypoint name and state as identified on FAA Form 8260-2 (e.g., ZELAK, WA). For routes, leave blank. For a departure procedure (DP) or standard terminal arrival route (STAR), enter the primary airport name.
i. Inspection Type. Click on the drop-down box and select the appropriate entry. An “I” prior to the code indicates an incomplete inspection.
TYPE INSPECTION CODE Periodic P Commissioning C Site Evaluation E Special S (3)
(1) Identify incomplete or partial inspections by clicking on the drop-down box and selecting the appropriate entry. Shipboard TACAN will always be a complete "Special" inspection. Select “S/ SBT”.
(2) All surveillance (SURV) inspections must be considered complete.
8240.36L 10/01/06
Page 12 Chap 2 Par 12i
(3) For special inspections, click on the drop-down box and select the appropriate entry. An “I” prior to the letter “S” indicates an incomplete inspection. The appropriate code that describes the type of special must follow the “S”. Available codes are as follows:
After Accident AA (see note below) Air Traffic Control and Landing TE Systems (ATCALS) Evaluation Antenna Change AC Discrepancy Found DF (During Surveillance Check) Frequency Change FX Memorandum of Agreement MA Maintenance Request MR Mobile/ Tactical Flight Inspection MT On Site Request OSR Procedures Check PROC Reconfiguration RF Shipboard TACAN SBT User Complaint UC Remove and Replace Like Equipment RR Radio Frequency Interference RFI Other (Explain in Remarks) OTHER
NOTE: Includes RADAR inspection involving a "near mid-air collision." See Order 8200.1, Chapter 14.
10/01/06 8240.36L
Chap 2 Page 13 Par 12j
j. Crew Information. These fields must contain the crew number (e.g., VN###) of the pilot-in-command of the mission, the second-in-command, the mission specialist, and any additional mission specialist. Reports containing multiple pages of the same form (i.e., VOR report containing multiple copies of FAA Form 8240- 2) require crew number and date on the first page only.
(1) Pilot-in-Command Crew Number Field. This field must contain the crew number of the pilot-in-command of the mission. When a flight inspection is accomplished over multiple dates, with different flight inspectors in charge, and the data obtained is combined on one report, this field must contain the crew number of the pilot-in-command during the final date of the check.
This crew number certifies the operational status of the facility and the degree to which the facility supports the approved instrument flight procedure(s) inspected. If only one crew number appears on the report, it certifies the completeness and accuracy of all reported data.
When a VOT is inspected using a portable ILS/ VOR receiver, the PIC crew number is required if there is a NOTAM issued as a result of the inspection. If a NOTAM is not issued, the PIC crew number is not required. In this instance, leave the PIC field blank.
(2) Second-in-Command Crew Number Field. This field must contain the crew number of the second-in-command. When a flight inspection is accomplished over multiple dates and the data obtained is combined on one report, this field must contain the crew number of the second-in-command during the final date of the check.
When a VOT is inspected using a portable ILS/ VOR receiver, the SIC crew number is not required. In this instance, leave the SIC field blank.
(3) Mission Specialist Crew Number Field. This field must contain the crew number of the mission specialist and certifies the reported technical data is complete, accurate, and conforms to national standards and specifications. The crew number of the mission specialist must be on all flight inspection reports unless his/ her participation is not required for the facility certification. In this case, enter "NA" in place of the crew number.
(4) Additional Mission Specialist Crew Number Field. This field must contain the crew number of any additional mission specialist.
k. Aircraft Number. Enter the aircraft registration number (e.g., N99).
l. Flight Inspection Field Office (FIFO) Field. In the FIFO field, enter the assigned 3-letter code of the location of the Pilot-in-Command (PIC) conducting the inspection. If the Army accomplished the inspection, enter “Army” in the field. For other non-FAA inspections, enter “Other” and explain in Remarks.
8240.36L 10/01/06
Page 14 Chap 2 Par 12m
m. Facility/ Approach/ Procedure Status Field. The appropriate facility status must be entered in accordance with Order 8200.1, Facility Status and Classification.
n. Remarks Field. See Chapter 3. 13. CORRECTED COPIES OF REPORTS. If a report must be changed, the originator must complete an amended version of the report. Each amended report must include the number of the amendment (e.g., Report Amended #1: or Report Amended #2) to identify reports that are amended more than once. If the report has been previously distributed, the annotation " Report Amended #2: " must be entered in the top margin of page 1 and the amended report forwarded to the Flight Inspection Central Operations (FICO) Technical Services Sub-Team (TSS) Flight Inspection Records Team, for redistribution. After accident (AA) reports, if amended, must have the annotation "Report Amended" (this date must be the date the report was amended) entered in the top margin of page 1 and the amended report forwarded to the TSS Flight Inspection Records Team for redistribution. The "AA" report with the latest amendment date is the final report. The TSS Flight Inspection Records Team must retain all after accident reports, including amendments. Any reports that cannot be interpreted by FICO TSS will be returned to the originating organization for clarification.
14. SECURITY CLASSIFICATION OF FLIGHT INSPECTION REPORTS
a. Guidance. The military organization requiring classification of flight inspection reports must provide classification guidance. The military organization will be requested to provide this guidance in writing, either by letter or message, and the guidance must be maintained on file so it can be traced to a classification authority who can 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, to show: 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; and, if an exemption category is provided, date the report can be declassified (if it can be determined). Specific marking instructions can be obtained from the servicing FAA security office.
c. Control of Reports. 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 TSS Flight Inspection Records Team, must contact the Civil Aviation Security Division, AMC-700, and obtain a security control number for all classified reports.
10/01/06 8240.36L
Chap 2 Page 15 Par 15
15. DISTRIBUTION OF REPORTS AND RECORDINGS.
a. General. The Technical Services Sub-Team (TSS) Flight Inspection Records Team must make the required distribution of all flight inspection reports (except those reports discussed in subparagraph 15c). Flight inspection units must forward all flight inspection reports within 60 days after finishing the flight inspection or portions of inspection (progressive periodics, incomplete inspections, etc.). All recordings will be forwarded within 15 days following notification of completion of processing and distribution from the TSS Flight Inspection Records Team.
(1) The cover page of each recording should be annotated with the following information: • Facility Identification and Type of Facility • Special Remarks, as appropriate (P, PM, PO, etc.) • Date(s) of Inspection • Type of Inspection, e.g., Periodic, Special, etc. • Aircraft Tail Number • Crew Member Numbers
This requirement may be satisfied by securely taping a copy of the first page of the flight inspection report to the top of the recordings.
(2) Securely tape the recordings (all 4 sides), or for a large stack of recordings, an envelope may be used.
(3) A copy of the data sheet applicable to the inspection, all paperwork, and worksheets should be placed inside the folds of the recordings.
(4) All packages must be shipped using boxes or fabric mailers. Padded envelopes must not be used. Shipping of recordings must be accomplished with a carrier allowing tracking of shipment.
(5) All packages must include a list of contents. As a minimum, include a list of facility IDs, facility type, and the date of the inspection. The Flight Inspection Field Office will retain a copy of the shipment list for their records and send a copy to the TSS Flight Inspection Records Team via Email. This notification will be kept in suspense until the package arrives. The shipment notification message should be sent to the TSS Flight Inspection Records Team at the following address: 9-AMC-AVN-Flight Inspection Reports/AMC/FAA.
8240.36L 10/01/06
Page 16 Chap 2 Par 15a
Distribution should be made at least bi-weekly by the U.S. Postal Service or
Federal Express. Ship the package to:
U.S. Postal Service Federal Express
FAA/ MMAC/ AJW-335A FAA/ MMAC/ AJW-335A ARB, Room 117 ARB, Room 117 P.O. Box 25082 6500 S. MacArthur Oklahoma City OK 73125 Oklahoma City OK 73169
b. After Accident (AA) Reports. After-accident reports, including FAA Form 8240- 14, Flight Inspection Report – After-Accident Continuation Sheet, must be forwarded to the TSS Flight Inspection Records Team within 3 days of completion of the inspection. Normal report completion procedures and local QC must be accomplished. The TSS Flight Inspection Records Team must forward the pending report to the FICO Technical Services Sub-Team where it will be reviewed and changes may be recommended. If satisfactory, it will be returned to the TSS Flight Inspection Records Team for archiving and distribution. If unsatisfactory, it will be returned to the originator for changes. The final report must be forwarded to the TSS Flight Inspection Records Team within 7 days of completion of the inspection. The TSS Flight Inspection Records Team must send the entire final AA Report, including FAA Form 8240-14 and the complete preceding periodic flight inspection reports, to the Technical Operations Service Area Flight Standards Accident Coordinator/ Investigation within 14 days of completion of the inspection. See Appendix 14 for review and completion requirements prior to the above distribution.
c. ILS/ MLS Maintenance Alert. Flight Inspection Central Operations must send an electronic copy of the report to the Technical Operations Service Area engineer or military command. Enter in Remarks who was notified. Send a copy to the TSS Flight Inspection Records Team, to be retained with the recordings. No further distribution is required.
d. RNAV Report Distribution. The TSS Flight Inspection Records Team will send a copy of all private special use reports to the proponent specified in the memorandum of agreement.
e. Obstacle Evaluation Form. The TSS Flight Inspection Records Team will send a copy to the National Flight Procedures Office.
f. Radio Frequency Interference Report. Results of Radio Frequency Interference (RFI) investigations will be included with the form designated for the type facility (i.e., RFI found on the ILS facility will be reported on FAA Form 8240-8, Flight Inspection Report-Instrument Landing System).
10/01/06 8240.36L
Chap 3 Page 17 Par 15g
g. Standard Distribution
(1) FAA
(a) Within the contiguous United States:
1 Service Area Office having jurisdiction over the facility inspected - one electronic copy.
2 Technical Operations having jurisdiction over the facilities inspected - one electronic copy.
(2) Military reports distribution for all Department of Defense (DoD) facilities will be emailed to the locations on file with the TSS Flight Inspection Records Team (AJW-335A). The TSS Flight Inspection Records Team will work with DoD locations for changes, corrections, and deletions of account information.
(3) International. Distribute reports to address provided by customer.
(4) General Characteristics Reports.
(a) Send an electronic copy to the TSS Flight Inspection Records Team.
(b) The TSS Flight Inspection Records Team must send an electronic copy to the appropriate military command for local distribution, an electronic copy to the Airport Authority responsible for the service, or any other entity as deemed appropriate.
(5) Radio Frequency Interference Reports. Send an electronic copy to Spectrum Engineering Services Office.
16 - 20. RESERVED
Chapter 3 - Req'd Report Remarks
8240.36L 10/01/06
Page 18 Chap 3 Par 21
CHAPTER 3. REQUIRED REPORT REMARKS 21. REMARKS FIELD. Briefly note any additional information required to indicate groundbased facility performance or space-based procedural inadequacies. For ground-based facilities, do not go into detail about the adjustments made to obtain final results unless the inspection was made especially to ascertain the effect of the adjustments or facility configurations (e.g., engineering projects).
a. Out-of-Tolerance Conditions.
(1) Identify and, if necessary, describe each out-of-tolerance or unsatisfactory condition found. This is not applicable for ILS parameters reported in Fields 6, 7, and 9 of FAA Form 8240-8, Flight Inspection Report--Instrument Landing System or Fields 6, 7, and 8 of FAA Form 8240-16, Flight Inspection Report--Microwave Landing System. Where there are no provisions to identify out-of-tolerance facility/ approach/ procedure performance (e.g., FAA Form 8240-2, Field 7), place an asterisk next to the “as left” data and a corresponding asterisk in the remarks with the initial out–of-tolerance value, or if necessary, describe the condition and/ or status (corrected/ uncorrected) of the condition.
(2) Indicate whether or not the condition was corrected.
(3) For military facilities, approaches, or procedures, include a statement that military personnel or units were briefed or advised and the date (e.g., tower/ maintenance briefed 4/26/89).
b. Facility, Approach, or Procedure Narrative. When narrative references are necessary to describe the facility/ approach/ procedure, factual statements of existing conditions must be used; do not attempt to determine causal relationships based on observations. For example:
(1) Observation (Permissible).
"The facility structure has deteriorated at 210°. Work was noted on a highway near the facility/ approach/ procedure in that sector."
(2) Unsubstantiated reference (Prohibited).
"The highway construction southwest of the facility/ approach/ procedure is causing deterioration of the course structure."
10/01/06 8240.36
Chap 3 Page 19 Par 21c
c. Site Evaluation, Commissioning, and Special Flight Inspection Reports. Remarks for these types of inspections must contain the special control number and/ or procedure number assigned by the FICO and sufficient detail to explain the extent of changes, modifications, and final results so they can be clearly understood by recipients of such reports. Additionally, for a maintenance request or on site request, include the reason for the inspection. Contents of this paragraph do not apply to shipboard TACAN inspections.
d. Notice to Airmen (NOTAM(s))/ Restrictions. Record NOTAM(s)/ Restrictions issued, revised, or cancelled as a result of the inspection. Reconfiguration flight inspections require revalidation of previous restriction(s) and, if necessary, issuance of new NOTAM(s)/ Restrictions as appropriate.
NOTE: During a reconfiguration flight inspection, cancel all existing restrictions and re-issue as necessary using the “Reconfiguration Date”.
Enter the NOTAM/ restriction as published (or as recommended for military facilities) and the date the NOTAM/ restriction information was forwarded to the FICO or appropriate organization. If the previous flight inspector issued the NOTAM or the facility, approach, or procedure restriction remains in effect and is not changed by the present inspection, enter, "NOTAM(s) (restriction) dated … remain in effect," in the Remarks section of NOTAM block. The Facility Status does not determine the requirement for this remark. However, once the NOTAM(s)/ restriction(s) information is included in the DOD Flight Information Publication, United States Government Flight Information Publication, or other appropriate publication, this remark is not required. The current NOTAM information as issued will be maintained in the AVNIS facility data.
e. Facility Status. If a facility/approach/procedure classification status is changed as a result of the flight inspection, enter appropriate remarks to identify the reason for the change along with a verbatim copy of the published NOTAM (see Paragraph 21d). Include who was notified and when.
f. Approach Lighting System. When commissioning an approach lighting system, either in conjunction with a NAVAID approach or as a separate system, enter the type of lighting system inspected and its status (e.g., ALSF-1, touchdown zone, and centerline lighting checked "satisfactory" or "unsatisfactory") (see Appendix 5, Paragraph j).
8240.36L 10/01/06
Page 20 Chap 3 Par 21g
g. Standard Instrument Approach Procedures (SIAP(s)). A periodic SIAP inspection includes all the standard requirements as listed in Chapter 6 of FAA Order 8200.1, except for the obstacle verification. If procedural changes do not require recorded data, (e.g., MDA raised, controlling obstacle changed with no change in minima, or fixes within the FISSV) include the statement, “No electronic data required.”
NOTE: If required, report the SIAP information in the following order: Airport name, city, state, SIAP(s), and amendment number (e.g., Tulsa Int’l, Tulsa OK, VOR Rwy 23, Amdt 1).
If one of the following circumstance(s) is applicable to the inspection of a SIAP(s), report the results of the inspection appropriately:
(1) Periodic Evaluation. Enter the following remark: "SIAP/ SIAP(s) verified IAW Order 8200.1, Chapter 6" or enter "SAT " or “UNSAT*” in dedicated SIAP block(s) when provided.
NOTE: SIAP(s) at U.S. airports do not require an obstacle evaluation to complete a periodic inspection; the runway “ROC Check” program fulfills this requirement.
(2) New or amended SIAP(s). Report the SIAP information with the statement "SIAP verified IAW Order 8200.1, Chapter 6."
(3) SIAP(s) not checked. If during a scheduled SIAP evaluation not all the SIAP(s) are checked, click on the drop-down box and select “SAT/ Incomplete*”. Record the SIAP information with the statement "SIAP not inspected." Additionally, if one or more of the SIAP(s) were found “UNSAT” click on the drop-down box and select SAT/ UNSAT*/ Incomplete*. Record the SIAP information for the SIAP(s) found unsatisfactory and describe the unsatisfactory condition in detail.
(4) SIAP found unsatisfactory. If during a scheduled SIAP evaluation a SIAP(s) is found unsatisfactory and one or more SIAP(s) are found satisfactory click on the drop-down box and select “SAT/ UNSAT*”. Record the SIAP information for the SIAP(s) found unsatisfactory and describe the unsatisfactory condition in detail.
(5) More than one SIAP is identified on a single page of the DOD Flight Information Publication or United States Government Flight Information Publication. The SIAP verification, when accomplished, must be entered on the appropriate form (i.e., If the SIAP is a compound type, such as an ILS/ TACAN RWY 17, report the ILS part on an ILS form and the TACAN part on a TACAN form).
(6) After Accident Reports. If the information is contained on the after accident continuation sheet, an entry in this field is not required.
10/01/06 8240.36
Chap 3 Page 21 Par 21h
h. AVNIS Facility Data. If the Location, Identifier, Owner, and/or Equipment are changed, show the revised data on the first facility inspection report following the change and remark, e.g., the former identifier was (indicate the identifier formerly shown). Flight inspection-initiated changes must be explained in the Remarks section, if appropriate.
i. Expanded Service Volume (ESV). Whenever the ESV is established or revalidated, define the lower limits of the ESV by facility component, azimuth/bearing (From) or beginning and ending azimuth/bearing if an arc is flown, distance and minimum reception altitude (MRA) (azimuth not required on ILS). (For example: VOR/ DME/ R-090/ 45 nm/ 16,000’ Revalidation, SAT or ILS/ L/ 6,000’-2,000’/ 28 nm ORIG. SAT). There is no requirement to report the upper limit of the ESV, unless interference is reported or suspected, or if requested specifically in FAA Form 6050-4, Expanded Service Volume Request. If requested in FAA Form 6050-4, both upper and lower limits are required for localizers and TLS azimuths. Include appropriate remarks regarding the status of the ESV check (i.e., if unsatisfactory, explain why). When establishing a fix, state whether the fix displacement area is SAT/ UNSAT. Indicate if the ESV check is an original request or a revalidation.
j. 75 MHz Marker Beacons that Support an Instrument Approach Procedure. The operation of 75 MHz markers must be documented on the report that certifies the primary NAVAID, (e.g., VOR, ILS, NDB).
(1) For commissioning checks of 75 MHz markers, changes of equipment or antennas, enter all checklist items checked and their status (e.g., "satisfactory" or "unsatisfactory"). If dual equipment is installed, document the minor axis width for both transmitters.
(2) For periodic type inspections, enter a statement to indicate the marker was checked satisfactorily (e.g., 75 MHz marker system(s) checked "satisfactory" or "unsatisfactory"). This statement is not required on reports that have 75 MHz fields (e.g., ILS reports).
(3) If any part of the 75 MHz marker system is unsatisfactory, annotate in this field.
k. Weather Broadcast Information. On commissioning reports only, list all weather broadcast capabilities for each facility inspected.
8240.36L 10/01/06
Page 22 Chap 3 Par 21l
l. Mobile/tactical facilities installed in support of a specific temporary (normally not to exceed 90 days) requirement will use a four-letter ID for reporting. Enter the four-letter ID in the ident field. Enter the transmitted ident, if different, in the Remarks section. The assignment of the four-letter ID(s) is as follows:
The first letter will always be an X The second and third letters will indicate the region where the temporary facility is located:
AL = Alaskan CE = Central CN = Canada EA = Eastern EU = Europe GL = Great Lakes IN = International (not otherwise coded) LC = Latin American/Caribbean NE = New England NM = Northwest Mountain PC = Asia/Pacific SO = Southern SW = Southwest WP = Western Pacific The fourth letter will indicate the owner
A = Air Force R = Army N = Navy/Marines C = Coast Guard EXAMPLE: XSWA = Mobile deployment of an Air Force asset located in the Southwest Region.
m. Other. Enter all other remarks required by the appendixes in this order.
n. Special Checks Which Meet Periodic Requirements. When a special check meets periodic requirements, enter the remark, “Periodic requirements met.” (Updating the periodic inspection following an after-accident inspection has to meet specific conditions—see Appendix 14, Paragraph 2c). If necessary, identify which transmitter was completed (e.g., xmtr #1—periodic requirements met; xmtr #2—out of service).
o. Critical Area Interference Checks. When a Critical Area Interference Check is accomplished, enter the following, “The FAA does not consider this flight inspection as a valid check of interference caused by aircraft/vehicles in the ILS critical zone.”
p. Structure Tolerance (95% Rule). Notify the FICO when structure tolerance (95% rule) is applied to a Category II/III facility. The FICO must notify the applicable region or military command engineering staff upon initial application of this criteria. Enter in Remarks the FICO was notified. (Ref Order 8200.1, Paragraph 15.51a.)
10/01/06 8240.36
Chap 3 Page 23 (and 24) Par 21q
q. RHO-THETA Magnetic Variation Change Inspection. Include 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 FICO Technical Services Sub-Team Aeronautical Information Specialist on FAA Form 8240-20.
r. Completion of an Inspection Previously Reported as Incomplete. Enter a statement indicating the check completes the inspection requirements of the report dated mm/dd/yy (e.g., This completes the requirements for the inspection dated 02/11/02).
s. RFI Checks. Enter a narrative description of checks performed and results obtained. Provide 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 aid another crew in locating the source.
t. 1800 RVR. If the data sheet contains an 1800 RVR authorization statement in the remarks and the system fails to meet the necessary criteria, add the following remark: “System does not meet the 1800 RVR requirements. FICO notified this date”.
22 - 25. RESERVED.
This Page Intentionally Left Blank
Appx 1 - FI Forms
APPENDIX 1. FLIGHT INSPECTION FORMS The FAA flight inspection report forms contained in this order are intended to be computer generated. If this process is not available, local reproduction of the forms included in each appendix is authorized.
FAA FORM
DATE FORMERLY
FAA FORM
TITLE
8240-1 7/2005 8240-1 Flight Inspection Report – Continuation Sheet
NOTE: Use this continuation sheet when additional space is required to document facility performance. Use the same heading information as in the primary report.
8240-2 10/2005 8240-2 Flight Inspection Report – VOR, VOR/DME, VORTAC, TACAN, VOT
8240-2 10/2005 New Form Flight Inspection Report – VOR, VOR/DME, VORTAC, TACAN, VOT – Radial Data
8240-4 7/2005 8240-4 Flight Inspection Report - VOR, VOR/DME, VORTAC, TACAN ORBITAL Data
8240-5 7/2005 8240-19 Flight Inspection Report – Non-Directional Beacon, Direction Finding, Visual Aids, Communications
8240-6 7/2005 8240-6 Flight Inspection Report – Precision Approach Radar
8240-6 7/2005 8240-6-1 Flight Inspection Report – Precision Approach Radar GPN-22 / TPN-25 Continuation Sheet
8240-6 7/2005 8240-6-2 Flight Inspection Report – Precision Approach Radar TPN-22 Continuation Sheet
8240-7 7/2005 8240-7 Flight Inspection Report - ILS Worksheet
8240-7-1 7/2005 8240-7-1 Flight Inspection Report - ILS Continuation Worksheet
8240-8 7/2005 8240-8 Flight Inspection Report – Instrument Landing System
8240-8 7/2005 New Form Flight Inspection Report – Instrument Landing System Azimuth Part I
8240-8 7/2005 New Form Flight Inspection Report – Instrument Landing System Azimuth Part II
8240-8 7/2005 8240-19 Flight Inspection Report - Endfire Glide Slope Transverse Structure Plot
FAA FORM
DATE FORMERLY
FAA FORM
TITLE
8240-11 7/2005 8240-11 Flight Inspection Report – ILS/ MLS Maintenance Alert
8240-12 12/2005 8240-12 Flight Inspection Report – Surveillance Radar
8240-13 10/2005 8240-13 Flight Inspection Report – General Characteristics
8240-14 7/2005 8240-14 Flight Inspection Report – After-Accident Continuation Sheet
8240-16 7/2005 8240-16 Flight Inspection Report – Microwave Landing System
8240-16 7/2005 Flight Inspection Report – MLS Commissioning Data Words
8240-17 12/2005 8240-5-1 Flight Inspection Report - RNAV
8240-21 10/2005 New Form Flight Inspection Report – Controlling Obstacle Evaluation
Page A1-3 (and 4)
FLIGHT INSPECTION REPORT
FAA FORM 8240-1 CONTINUATION SHEET
This Page Intentionally Left Blank
APPENDIX 2. FLIGHT INSPECTION REPORT
Appx 2 - VOR Report
VOR, VOR/ DME, VORTAC, TACAN, VOT,
FAA FORM 8240-2 Record the following:
a. Field 1 - Flight Inspection Report Header. Complete as shown in Chapter 2, Paragraph 12.
b. Field 2 - Aircrew Information. Complete as shown in Chapter 2, Paragraph 12.
c. Field 3 - Facility Information.
(1) VOR, TACAN, DME Coverage, DME Accuracy, and VOT Fields. Click the appropriate drop-down box to signify all components of the facility being reported. When a VOT is inspected using a PIR, choose “Inspected/ PIR” from the drop-down box. For DME, also indicate the status of the inspection (i.e.”SAT” or “UNSAT”).
(2) Voice, Standby Power, and Ident. If any of these items are inspected, click on the drop-down box and select the appropriate entry.
(3) Type Facility. Click on the drop-down box and select the appropriate entry to indicated the type facility.
(4) Facility Status. Click on the drop-down box and select the appropriate entry.
(5) SIAP(s) Verified. Complete as shown in Chapter 3, Paragraph 21. Click on the drop-down box and select the appropriate entry.
d. Field 4 - NOTAM(s). Complete as shown in Chapter 3, Paragraph 21d.
e. Field 5 - Remarks. Complete as shown in Chapter 3. Additionally, after commissioning or reestablishing a receiver checkpoint, describe it in this field. Include the airport name and state (if on an airport), altitude at which check is made (airborne checkpoints), azimuth in degrees magnetic, the distance in miles and the checkpoint description (e.g., Ground Checkpoint: University of IL-Willard, IL, 332°, 0.9nm, on runup pad Rwy 14: Airborne checkpoint: 2000’, 175°, 8.0nm, over grain elevator at Pesotum; VOT reference point: Approach end of Runway 35R). Notify the FICO Aeronautical Information Specialist, via FAA Form 8240-20 (fill out form IAW the Aeronautical Data Management Order) of the establishment or cancellation of receiver checkpoints.
(1) Radial Alignment. Report when radial alignment is authorized by Flight Inspection Policy in lieu of an alignment orbit.
(2) VOT. When commissioning a VOT, indicate the identification feature (dots or steady tone).
(3) USAF VOR(s). For USAF VOR(s), enter the modulation values found on at least one radial or arc segment flown during the inspection. These values must be reported in the following format: modulations/ radial flown or arc/ start - stop radials/ distance(s) to the nearest mile/ MSL altitude divided by 100. Radial example: 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.
(4) Reference Alignment. Indicate the date Maintenance was notified of ARR/ orbit reference alignment establishment/ re-establishment, IAW Order 8200.1, Chapter 11.
(5) VOT Inspected Using a Portable ILS/ VOR Receiver.
(a) Record the PIR detected course deviation, modulation levels, and signal strength.
(b) Record the model, serial number, and calibration date of the PIR.
(c) Add the following statement, “Aviation System Standards Flight Inspection Technical Services Sub-Team authorized VOT flight inspection via PIR.”
(d) Do not add any data in Field 7C (Radial Data) of FAA Form 8240-2- 2.
(e) Place an asterisk in the “Aircraft Number” field.
f. Field 6 - Flight Inspection Data. Complete Fields 6A and 6B when the reference radial and mean orbital alignment is established/ re-established. Do not report the reference radial data without the alignment orbit, or vice-versa. This field should also be completed when there is a need to permanently change flight profiles, e.g., direction, distance and /or altitude. Enter the azimuth monitor evaluation results when accomplished. The Flight Inspection Central Operations Team (FICO) Aeronautical Information Specialist will transfer data from the flight inspection report to the AVNIS data sheet whenever there is a date entered in the “Date Established” Field. For a periodic with orbit inspection, report the orbital data in 6A. Do not enter a date into the “Ref Date” field when reporting periodic data, unless it is also a reference orbit. When out of tolerance condition(s) are found during an orbit, Field 8, Orbital Data, must be reported.
(1) Orbital Data. Enter the mean alignment (e.g., + 0.2). Enter the maximum negative and the maximum positive alignment error (include the sign). Following entry into the maximum negative and the maximum positive fields, FIRPS will automatically calculate and enter the “spread”. Enter the orbit direction (CW or CCW) under the DIR field. If a
constant altitude is flown throughout the orbit, enter the altitude divided by 100 in this field. If altitude changes occurred during the orbit, enter a remark in Field 5 - Remarks indicating 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 mile. If the distance changed during the alignment orbit, enter a remark in Field 5-Remarks indicating the distance changes and the radials where the distance change occurred (e.g. Distance changed on alignment orbit 9/ 015-090, 8/ 091-135, etc). Enter the date when a reference orbit is accomplished (month, day, and year; 01/04/05).
(2) Reference Radial/ Monitor. Using the radio button, 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 radial data field of the report.
(a) Reference Radial. For AFIS, enter the azimuth, the segment distance (to the nearest mile), and the altitude flown divided by 100 (e.g., 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 a VOT, enter the azimuth 360°/ from (e.g. 360/ from).
(b) Checkpoint. Enter the location where the monitors were evaluated. If evaluated airborne, enter the location as done for the reference radial. If monitors are checked where the reference checkpoint/ radial was evaluated, enter "Same." If the monitors are established on the ground, enter the azimuth and distance of the airport location and the term "Gnd" (e.g., 041.1/6.7/Gnd). Describe the airport location in the Remarks field (carrying forward the airport location on subsequent reports is optional). For a VOT, enter "VRP" if VOT Reference Point is used for monitor evaluation. If not, enter an * and describe, in Remarks, the checkpoint location where the monitor evaluation was accomplished.
(c) Tx, Alignment, Alarm +, Alarm -. Use the appropriate blocks to report the results of the reference radial/ monitors.
1 Enter the transmitter evaluated under "TX." If a facility has two transmitters and both are checked, enter the transmitter number as in the example for Dual Transmitter. 2 Enter the “normal condition” alignment error determined at the reference radial/ checkpoint, or ARR if AFIS is used, in the Reference Radial “Alignment Column”. 3 When monitors are checked, enter the amount of shift (+ is clockwise, AFIS code "R"; - is counterclockwise, AFIS code "L") in the Checkpoint "Alarm +" and "Alarm -" 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 example.
SINGLE TRANSMITTER
TX ALIGNMENT ALARM + ALARM -
Reference Radial 265.5/ 18.3/ 45 1 -0.4
Checkpoint Same 1 0.9 0.9
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 (d) Date Established. Enter the month, day, and year that the reference radial alignment was established/ re-established for each facility/ component checked. When an inspection is conducted over multiple dates, do not enter a date until the check is complete. The date entered will be the final date of the inspection. (Example: Dates entered in Field 1 are: 10/18, 11/12-14, 11/21/94; the date to be entered in " Date Established" is: 11/21/94). To maintain continuity of data, carry forward the information on each succeeding check until the flight check is complete, then include the final date of the inspection in the “Date Established” Field. Do not enter a date for monitor checks if it was not accomplished concurrently with the establishment of the reference radial/ alignment orbit.
g. Field 7 - Radial Data
(1) Service Designation. Click on the drop-down box and select the appropriate entry.
(2) Radial Use. Indicate radial use by an abbreviation (if no procedural use, leave the block blank). Do not use “ESV,” as it does not describe procedural use. Other abbreviations may be used if explained in "Remarks" portion of report. When using the automated form, a drop-down box is available for radial use selection. Some standard examples are as follows:
ARR Automated Flight Inspection System (AFIS) Reference Radial Ref Reference Radial V16 Airway GCP Ground Receiver Checkpoint ACP Airborne Receiver Checkpoint Apch Approach IApch Initial Approach MApch Missed Approach Hold Holding Pattern J180 Jet Route Dir Direct Route RNAV Area Navigation (RNAV) Procedures Null Null Radial 5DEG Offset (Special Check) of VOR APCH FEDR Feeder INTX Radial Used to Support a Fix or Intersection STAR Standard Terminal Arrival Route SID Standard Instrument Departure COV Coverage Radial DP Departure Procedure
(3) 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). For a VOT, designate azimuth as "360/from."
(4) Transmitter (s). Identify the transmitter checked. If transmitters were alternated during one flight, enter the transmitter "1" or "2" first (whichever had the greatest alignment error, in the "transmitters" block (e.g., 2/1 for TX 2 having the greatest error).
(5) 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., 25/20). Leave blank when reporting ground checkpoints.
(6) Distance From/ To. Show the starting point (From) and the termination point (To) in nautical miles from the facility.
(7) Roughness and Scalloping, Bends, and Polarization. If these parameters are in tolerance, enter the maximum amplitude to the nearest tenth of a degree and indicate the distance from the station (e.g., 2.2/ 16.0). If these parameters are out-of-tolerance, enter the out-of-tolerance (amplitude/distance) closest to the facility. When reporting radial roughness and/or scalloping that exceeds 3.0° but meets operational tolerances because of the distance and altitude criteria, report the worst case of actual roughness and scalloping, the mileage where it occurred, and place an asterisk in the reporting block, e.g., *5.0°/25.5. In the Remarks section, place a corresponding asterisk and state "Order 8200.1, Paragraph 11.60a or 11.60b applied." If multiple distance segments require separate entries, enter in the remarks section. The reported scalloping and roughness is combined. For RNAV procedures, report the azimuth of the maximum roughness and scalloping (e.g., 1.5/ 010).
(8) Bends/ CMA and Bends. 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 at which it occurs (e.g. + 1.2/ 15.6). If these parameters are out-of-tolerance, enter the out-of-tolerance (amplitude/ distance) closest to the facility. If multiple segments require separate entries, enter in remarks section.
(9) Polarization. Enter an “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in Remarks.
(10) Alignment Error. Enter the alignment error, as a "+" or "-" value, and the distance from the facility at which it occurs. If automated flight inspection system (AFIS) average alignment is reported, indicate the alignment and distance, to the nearest mile, throughout the entire area that was sampled (e.g., + 0.5/10-65). Enter "SAT" for satisfactory or "UNSAT" for unsatisfactory when approach alignment evaluations are by visual references to runway thresholds or airport environments. When an RNAV procedure is evaluated using AFIS orbital techniques, enter the average orbit alignment error.
(11) Modulations. Enter "SAT" for satisfactory or "UNSAT" for unsatisfactory. USAF VOR modulation values shall also be entered in Remarks.
(12) Transmitter Difference. Enter the difference of course alignment between transmitters, to the nearest tenth of a degree.
(13) Signal Strength. If satisfactory, enter the actual value of the lowest VOR signal strength in microvolts. Signal strength exceeding 300 μV may be reported as 300+. Report TACAN signal strength as Satisfactory “SAT” or Unsatisfactory “UNSAT*”. If VOR or TACAN signal strength is unsatisfactory, enter “UNSAT*” and the closest distance from the facility it occurred, e.g., UNSAT*/ 25.
(14) Interference. Enter "SAT" if no interference noted; enter "UNSAT*" if interference is noted, and document the area of interference in remarks field.
h. Field 8 - Orbital Data
(1) Transmitter Number (No). Click the appropriate transmitter radio button for VOR and the appropriate transponder radio button for TACAN.
(2) DME Distance Unlock. Click inside the check box when there is an unlock(s) and list the azimuth(s) at which they occur (e.g., 012-023, 350-001) in the Field 8B block.
(3) TACAN Azimuth Unlocks. Click inside the check box when there is an unlock(s) and list the azimuth(s) at which they occur (e.g. 012-023, 350-001) in the Field 8C block.
(4) Area of interference. Click in the check box when there is an area of interference observed, if such interference is considered to have detrimental effect on the usability of the facility. List the azimuth(s) at which the interference was observed (e.g. 012-023, 350-001) in the Field 8D block.
(5) VOR Azimuth exceeds 2.5°. Enter the maximum course displacement observed when the course displacement exceeds ± 2.5° and azimuth of occurrence under the appropriate field. Each field represents 10° (e.g., under “00” field, an entry of azimuth alignment from 000 - 009 is possible and under “10” field, an entry of 010-019° is possible, etc.). Example: VOR azimuth exceeded 2.5° at 006-009° with maximum couse displacement occurring at 006°. Under the “00” field, enter azimuth = 2.6/ 006. VOR course displacement exceeds 2.5° at 013-039°. Under the ”10” field, enter 2.6/ 013; under the “20” field, enter 2.7/ 023, and under the “30” field, enter 2.6/ 039.
(6) TACAN Azimuth exceeds 2.5°. Enter the maximum course displacement observed when the course displacement exceeds ± 2.5° and azimuth of occurrence under the appropriate field. Each field represents 10° (e.g., under “00” field, an entry of azimuth alignment from 000 - 009 is possible and under “10” field, an entry of 010-019° is possible, etc.). Example: TACAN azimuth exceeded 2.5° at 006-009° with maximum couse displacement occurring at 006°. Under the “00” field, enter azimuth = 2.6/ 006. TACAN course displacement exceeds 2.5° at 013-039°. Under the ”10” field, enter 2.6/ 013; under the “20” field, enter 2.7/ 023, and under the “30” field, enter 2.6/ 039.
(7) VOR Coverage – Signal Strength (Document levels below -93 dbm). If the VOR signal strength drops below -93 dbm or 5μV, enter the lowest value that occurred under the appropriate field. Each field represents 10° (e.g. under “00” field an entry of the lowest signal strength below -93 dbm or 5μV from 000 - 009 is possible and under “10” field an entry of the lowest signal strength below -93dbm or 5μV from 010-019° is possible, etc). Example: A signal level of -110 dbm occurred at 015 - 019°. The appropriate entry is - 110 under the “10” field.
(8) TACAN Coverage-Signal Strength at which Azimuth or Distance Unlock Occurs. For U.S. Navy shipboard TACAN(s) and other TACAN(s) or DME(s), enter the TACAN or DME signal strength when the signal strength drops to a level which causes a condition of azimuth or distance unlock under the appropriate field.
Appx 2 - VOR Report › VOR, 8240-2
FLIGHT INSPECTION REPORT--VOR, VOR/DME, VORTAC, TACAN, VOT
FAA FORM 8240-2
8240.36L 10/01/06
Appendix 2
7. VOR, VOR/DME, VORTAC, TACAN, VOT - RADIAL DATA
Service Designation Radial Use Azimuth Transmitter(s) MSL Altitude Distance From Distance To Roughness/Scalloping Bend/CMA Bends Polarization Alignment Error Modulations Transmitter Diff. Signal Strength Interference
Service Designation Radial Use Azimuth Transmitter(s) MSL Altitude Distance From Distance To Roughness/Scalloping Bend/CMA Bends Polarization Alignment Error Modulations Transmitter Diff. Signal Strength Interference
Service Designation Radial Use Azimuth Transmitter(s) MSL Altitude Distance From Distance To Roughness/Scalloping Bend/CMA Bends Polarization Alignment Error Modulations Transmitter Diff. Signal Strength Interference * Remarks are required for fields marked with an asterisk FAA Form 8240-2 (v1.0 10-2005) Supersedes previous edition PAGE 2 OF 2
Page A2-11 (and 12)
This Page Intentionally Left Blank
Appx 3 - 4 (Reserved
10/01/06 8240.36L
Appendices 3 – 4
RESERVED
This Page Intentionally Left Blank
APPENDIX 5. FLIGHT INSPECTION REPORT—
NONDIRECTIONAL BEACON, DIRECTION FINDING, VISUAL AIDS, COMMUNICATIONS,
FAA FORM 8240-5 This report will be used to report the results of all commissioning, periodic, special inspections, and after accidents of the aids listed above. Changes to facility status or restrictions for NDB(s) used only as Compass Locators will be reported on both an FAA Form 8240-5 and an FAA Form 8240-8. The periodic and special inspections of visual aids or NDB(s) that support an ILS system will be reported on FAA Form 8240-8, except when the inspection of the visual aid or NDB is independent of the ILS. In this instance, use FAA Form 8240-5 for the report. If the NDB is used as a compass locator for an ILS, and the NDB also supports an NDB approach, two reports are required when the periodic is also conducted on the NDB approach. If the inspection only encompasses the NDB stand-alone approach, only the NDB report is required. All bearings will be reported as “FROM” the facility, unless there is a specific need to report them as “TO” the facility. Any bearings reported as “TO” the facility will be clearly indicated.
Appx 5 - NDB, Comm, DF
NOTE: Lights which do not support lower minima (e.g., LIRL, MIRL, PAPI, VASI, REIL) are not associated with the SIAP. Lights required for lower than one (1) mile visibility (nonprecision approach) or ¾ mile visibility (precision approach) or supporting lower than Category I (approach lights, TDZ, RCL, HIRL when runway visual range (RVR) required) are associated with the SIAP and should be reported on the associated facility form.
1. Field 1 – Flight Inspection Report Header. Complete as shown in Chapter 2, Paragraph 12, except for the following:
a. Identifier (Ident)
(1) For NDB and DF, enter the facility identifier listed on the AVNIS Facility Data Sheet.
(2) For Instrument Flight Rules (IFR), airport night evaluations, and general airport lighting (i.e., taxiway lighting), use the International Civil Aviation Organization (ICAO) airport identifier.
(3) For CONUS visual aids, enter the AVNIS runway identifier. Runway lighting systems (High Intensity Runway Lights (HIRL(s)), Medium Intensity Runway Lights (MIRL(s)), centerline lights, etc.) may require two reports, one report for each end of the same runway (e.g., KSNA 19R and KSNA 01L).
(4) For international visual aids, including runway lighting systems, enter the AVNIS runway identifier.
(5) For Charted Visual Flight Procedures (CVFP(s)), enter the ICAO airport identifier. Multiple procedures to the same airport may be reported on one report form.
(6) For communications, enter the AVNIS identifier for the facility being checked (e.g., KSLC, ZLA).”
8240.36L 10/01/06
b. Location. Complete as shown in Chapter 2, Paragraph 12, and include the NDB name, in parenthesis, if different than the NDB location name. For charted visual flight procedures (CVFP(s)), enter the location listed in the SIAP information. 2. Field 2 - Crew Information – Complete as shown in Chapter 2, Paragraph 12. 3. Field 3 - Facility Information. Indicate facility/ component inspected, status or as left condition as appropriate.
a. Direction Finding. Click on the drop-down box and select the appropriate entry.
b. Communications. Click on the drop-down box and select the appropriate entry.
c. Visual aids. Click on the drop-down box and select the appropriate entry. For CVFP(s), select an entry in this field.
d. NDB. Click on the drop-down box and select the appropriate entry.
e. NDB/ DME. Click on the drop-down box and select the appropriate entry.
f. Facility Status. Complete as shown in Chapter 2, Paragraph 12. Click on the dropdown box and select the appropriate entry. For Communications inspections, leave blank.
g. SIAP(s) Verified. Click on the drop-down box and select the appropriate entry. 4. Field 4 - NOTAM(s). Complete as shown in Chapter 3, Paragraph 21d. If the NDB is associated with an ILS, the restrictions shall be added to the ILS AVNIS data sheet. 5. Field 5 - Remarks. Complete as defined in Chapter 3.
a. Nondirectional Beacons. When routes are flown, enter the bearing, altitude, and distance flown (e.g., 030/ 2800/ 45.0). When the NDB is also used as a compass locator associated with an ILS system, enter the ILS identification on commissioning reports only (e.g., compass locator/ LOM/ LMM associated with RGR ILS).
b. Visual Aids. Indicate if the inspection was conducted at night (e.g., "runway end identifier lights (REIL) evaluated at night). Omission of this remark will indicate the check was conducted during the daytime. If the visual aid supports an ILS procedure, enter the ILS identification on commissioning reports only (e.g., approach lighting system (ALS) supports RGR ILS).
6. Field 6 - Flight Inspection Data
a. Nondirectional Beacon
(1) Radio Class Code. Enter the applicable code as it appears in the FAA AVNIS data unless information is changed by the report. Identify UHF facilities by adding "UHF." If inspecting the DME only of an NDB/ DME, leave blank.
(2) Frequency. Enter the published frequency of the NDB.
(3) DME Channel. If an NDB/ DME is inspected, enter the published DME channel.
(4) Identification. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(5) Coverage. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(6) Station Passage. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(7) Interference. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(8) Oscillations. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(9) Standby Equipment. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(10) Voice. If voice is inspected on a periodic inspection, indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriated entry. A (SAT) entry indicates all available voice capabilities for the facility (ATIS, AWOS/ASOS, etc.) are satisfactory. If (UNSAT) for one or more voice capabilities, explain in Remarks.
(11) Bearing Accuracy. The bearing accuracy block may be left blank, except for UHF homing beacons. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriated entry.
(12) Standby Power. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriated entry.
8240.36L 10/01/06
b. Direction Finding
(1) Station Passage. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriated entry. If not required, leave blank.
(2) Standby Power. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriated entry. If not checked, leave blank.
(3) Checkpoint. For AFIS, leave blank. For manual, describe checkpoints in Remarks.
(4) Aircraft Altitude. Enter the aircraft's altitude over the checkpoint, divided by 100 (e.g., "50" for 5,000 ft).
(5) Aircraft Distance. Enter the distance of the aircraft from the antenna to the nearest mile.
(6) Bearing/Aircraft. Enter the aircraft's magnetic azimuth, to the nearest degree from the direction finding (DF) antenna, when the DF bearing is given.
(7) Bearing/DF. Enter the bearing, to the nearest degree, issued by the controller.
(8) Bearing/Error. Enter the difference between the aircraft azimuth and the bearing issued by the controller to the nearest whole degree (e.g., aircraft azimuth 331°, issued bearing 333°, the error is -2°).
(9) Frequency Used. Enter the frequency used to obtain the DF bearing.
NOTE: Whenever an alignment orbit is flown (e.g., commissioning check, maintenance request, and as determined by the flight inspector), it may require several pages of DF checkpoints to satisfy the requirements of a complete orbit.
c. Visual Aids
(1) Facility Inspected. Click the appropriate check box to indicate the facility or facilities inspected. If the visual system inspected is not of the type covered by the four blocks, click the “Other*” check box and describe in Remarks.
NOTE: More than one type of visual system may be indicated in this field, provided the flight inspector shows clearly which facility each entry refers to and the entries in paragraph 1a, 1g, 1f and 1h are common to each facility. If these provisions cannot be met, complete separate forms.
(2) Runway(s) Served. Enter the numerical (and alphabetical when appropriate) designators which have been published to identify the runways served by the system(s) being reported.
(3) Glide Slope Angle
(a) When an angle is determined by flight inspection, enter the commissioned angle and the angle determined during the inspection into the "glide slope angle" block (e.g., 3.00°/ 2.95°), or
(b) When the commissioned angle is unknown and/or the angle is not determined during the inspection, enter an asterisk into the "glide slope angle" block (e.g., */ *) and explain in the "Remarks" field.
(c) Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriated entry.
(d) For PAPI(s) systems, report individual box angles in Remarks field. Example: For 2-box system, enter: Box 1 = 3.25°, Box 2 = 2.75°. For 4-box system, enter only the angles of Box 2 and Box 3 (i.e., Box 2 = 3.17°, Box 3 = 2.83°).
(4) Intensity. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(5) Angular Coverage. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(6) Sequence Flashers. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(7) Obstacle Clearance (VGSI). Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(8) Focus and Adjustment. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(9) Coincidence (PAR/ILS/MLS). Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(10) Runway Lights. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
(11) Radio Control System. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriate entry.
d. Communications. Click the appropriate check box to indicate the facility inspected. In cases where Pilot-to-Forecaster or Combined Station Tower was checked, click the P/ F or CS/ T check box and click the check box in the "other" block. Several frequencies may be listed on one line when the results placed in the blocks on that line are common to all frequencies listed. Indicate whether satisfactory (SAT) or unsatisfactory (UNSAT*) by clicking the drop-down box and selecting the appropriated entry.
Appx 5 - NDB, Comm, DF › 8240-5
Page A5-7 (and 8)
FLIGHT INSPECTION REPORT NDB, DF, VISUAL AIDS, COMMUNICATIONS
FAA FORM 8240-5
This Page Intentionally Left Blank
APPENDIX 6. FLIGHT INSPECTION REPORT
PRECISION APPROACH RADAR, GPN-22 /TPN-25 CONTINUATION SHEET,
TPN-22 CONTINUATION SHEET,
FAA FORM 8240-6, Complete one FAA Form 8240-6, Precision Approach Radar, per runway identifier. Always complete the primary Form 8240-6, and when necessary, complete the appropriate PAR Continuation Sheet, depending on PAR equipment type. 1. Field 1. Flight Inspection Report Header. Complete as shown in Chapter 2, Paragraph 12, except for the following:
Appx 6 - PAR
a. Identifier (Ident). Enter the ident listed in AVNIS for the specific runway. Report only one runway identifer per report.
b. Runway. Enter the applicable runway designator 2. Field 2. Crew Information – Complete as shown in Chapter 2, Paragraph 12. 3. Field 3. Facility Information
a. Controller Performance. Click on the drop-down box and select the appropriate entry to show that the item was inspected and that it did or did not meet operational tolerance.
b. ILS/ MLS/ VGSI Coincidence. Click on the drop-down box and select the appropriate entry to show that the item was inspected and that it did or did not meet operational tolerance.
c. Standby Equipment. Click on the drop-down box and select the appropriate entry to show that the item was inspected and that it did or did not meet operational tolerance.
d. Standby Power. Click on the drop-down box and select the appropriate entry to show that the item was inspected and that it did or did not meet operational tolerance.
e. Lighting System(s). Click on the drop-down box and select the appropriate entry to show that the item was inspected and that it did or did not meet operational tolerance.
f. Frequencies Used. List the frequencies inspected in the appropriate block (i.e., Found Sat or Found Unsat). If additional space is needed, enter in Remarks.
g. Facility Status. Complete as shown in Chapter 2, Paragraph 12. Click on the dropdown box and select the appropriate entry.
h. Published Angle. In the "Published Angle" block, enter the commissioned angle.
i. Published Alternate Angle. Enter the published alternate angle if one is approved.
j. Equipment Type. Enter the type of equipment inspected (e.g., MPN-14K, GPN-22, or TPN-19). 4. Field 4. Generic PAR Approach Run Configurations. Do not enter data in this field when using a PAR Continuation Sheet for other than generic PAR(s).
a. Approaches
(1) Moving Target Indicator (MTI). Click the check box to indicate if MTI feature was used during the approach.
(2) Polarization. Click the check box to indicate the type of polarization used during the approach (e.g., for circular polarization (CP)/ Rain or linear polarization (LP)/ Clear). For computer-generated radars, enter circular polarization (CP).
(3) Transmitter Used. Click the drop-down box and select the appropriate entry.
(4) Angle (Actual Angle). In the "Angle" block, enter the measured PAR angle for each transmitter that was checked. If the “Actual Angle” was not inspected, leave blank.
(5) SAT/ UNSAT. Click on the drop-down box and select the appropriate entry to show if the approach was satisfactory or unsatisfactory.
(6) The "Checks " columns shows which runs are necessary to satisfy commissioning and periodic requirements. 5. Field 5. NOTAM(s). Complete as shown in Chapter 3, Paragraph 21d. 6. Field 6. Remarks. Complete as defined in Chapter 3. Enter additional remarks, such as:
• When PAR equipment has been replaced or when a major modification has been performed.
• When MTI is required on the final approach. (This requirement does not constitute a facility restriction.)
7. Field 7. Flight Inspection Data:
a. Azimuth Radar. Click on each designated transmitter drop-down box and select the appropriate entry to indicate that an item was inspected and that it did or did not meet operational tolerance.
b. Elevation Radar. Glide Slope Alignment, Range Accuracy and Coverage. Click on each designated transmitter drop-down box and select the appropriate entry to indicate that an item was inspected and that it did or did not meet operational tolerance. 8. Flight Inspection Report--Precision Approach Radar Continuation Sheets. When required, complete a separate form for each runway inspected.
NOTE: Form abbreviations used in FAA Forms 8240-6 continuation sheets are as follow:
FTC - Fast Time Constant ACQ - Acquisition MTI - Moving Target Indicator RWY - Runway CK'S - Checks Required NOR - Normal BK UP - Back Up AUTO - Automatic COH - Coherent NON-COH - Noncoherent CFAR - Constant False Alarm Rate ALS - Automatic Landing Subsystem S/N - Serial Number C - Commissioning P - Periodic RCVR CHAN, RC - Receiver Channel
8. Flight Inspection Report—Precision Approach Radar GPN-22/ TPN-25 Continuation Sheet
a. Field 1 General. Runway. Enter the applicable runway designator.
b. Field 2. Computer Generated Precision Approach Radar Run Configurations
(1) “R”s indicate the required configuration for each run.
(2) Click the appropriate blocks to show which configuration was actually checked.
(3) Transmitter Used. Click the drop-down box and select the appropriate entry.
(4) Angle (Actual Angle). In the "Angle" block, enter the measured PAR angle for each transmitter that was checked. If the “Actual Angle” was not inspected, leave blank.
(5) RUN “SAT” or “UNSAT”. Click on the drop-down box and select the appropriate entry to show if the approach was satisfactory or unsatisfactory.
(6) The "Checks " columns shows which runs are necessary to satisfy commissioning and periodic requirements.
c. Field 3. Other Information. Enter receiver sensitivity, clutter (rain) reject, etc., in the blocks provided, as required in Order 8200.1, Paragraph 14.23b. 9. Flight Inspection Report--Precision Approach Radar TPN-22 Continuation Sheet
a. Field 1 – General
(1) Runway. Enter the applicable runway designator.
(2) System Serial #. Enter the serial number provided by Maintenance.
b. Field 2 - Computer Generated Precision Approach Radar Run Configurations.
(1) “R”s indicate the required configuration for each run.
(2) Click the appropriate blocks to show which configuration was actually checked.
(3) The “Checks ” columns show which runs are necessary to satisfy commissioning and periodic requirements.
c. Field 3 - Enter program data as required in Order 8200.1, Paragraph 14.23c. Enter transmitter output power and receiver sensitivity values provided by Maintenance.
Appx 6 - PAR › PAR, 8240-6
FLIGHT INSPECTION REPORT--PRECISION APPROACH RADAR
FAA FORM 8240-6
FLIGHT INSPECTION REPORT--PRECISION APPROACH RADAR
GPN-22 / TPN-25 CONTINUATION SHEET
Page A6-7 (and 8)
FLIGHT INSPECTION REPORT—PRECISION APPROACH RADAR
TPN-22 CONTINUATION SHEET
This Page Intentionally Left Blank
Appx 7 - ILS Worksheet
APPENDIX 7. FLIGHT INSPECTION REPORT
ILS WORKSHEET, FAA FORM 8240-7 AND ILS CONTINUATION WORKSHEET, FAA FORM 8240-7-1 This form must be used on all ILS flight inspection evaluations and may be handwritten. It must be retained with the corresponding recordings. The quantity of information entered on this form is not mandatory but should contain sufficient detail to explain the checks completed and the results found. 1. FAA Form 8240-7, ILS Worksheet
a. Field 1 - Location. Complete as shown in Chapter 2, Paragraph 12.
b. Field 2 - Identification (Ident). Enter the 3-letter identifier of the ILS facility being inspected.
c. Field 3 - Runway No. Enter the runway designator served by the ILS.
d. Field 4 – Date. Enter the date(s) of the checks.
e. Field 5 - Owner. Complete as shown in Chapter 2, Paragraph 12.
f. Field 6 - Type Check. Complete as shown in Chapter 2, Paragraph 12.
g. Field 7 - Facility Inspected. Place an “X” in the appropriate block(s) to signify components have been inspected.
h. Field 8 - Facility Status. Enter an “X” in the appropriate block for the localizer front course (F/C), glide slope (GS), and localizer back course (B/C) if inspected.
i. Field 9 - Localizer Data
(1) Width: Enter commissioned course width
(2) CAT: Enter Category
(3) B: Enter Cat I or Cat II commissioned course width + 17% or CAT III commissioned course width + 10%
(4) S: Enter Cat I or Cat II commissioned course width - 17% or CAT III - 10%
(5) Dual Freq: Enter Yes or No
(6) Dual Tx: Enter Yes or No
(7) Voice: Enter Yes or No
(8) ESV: Enter Yes or No
(9) Back Course: Circle Y or N.
j. Field 10 - Glide Slope Data
(1) Angle: Enter commissioned angle
(2) CAT: Enter category of facility
(3) H: Enter high angle limit (+ 10% for CAT I and II, + 4% for CAT III)
(4) L: Enter low angle limit (- 7.5% for CAT I and CAT II, - 4% for CAT III)
(5) GS Type: Enter glide slope equipment type (null reference, capture effect, etc.)
(6) Dual Tx: Enter Yes or No
(7) ESV: Enter Yes or No
(8) GRD Temp: Enter temperature used when conducting ILS-2 runs
(9) OAT: Enter temperature used when conducting ILS-2 runs
(10) Baro: Enter barometric pressure used when conducting ILS-2 runs
(11) Alt: Enter MSL altitude ILS-2 runs were flown.
k. Field 11 - Notes: Enter any additional information that may be useful in interpreting the results of the flight inspection (e.g., the calibration values, distances, altimeter setting, etc.)
l. Field 12 - Enter in chronological order the checks conducted and the results. Use enough detail that a qualified person can interpret the information and correlate the data to the flight inspection recordings.
(1) Run Number (#). Enter the numerical sequence of each check or test.
(2) Facility Configuration (CFG). Enter the number of the transmitter being inspected and the transmitter configuration code as listed below:
Localizer Transmitter Configuration Code
Normal N Special Requirements Z Alignment Alarm Left L Alignment Alarm Right R Course Width Wide W Course Width Narrow S RF Power Alarm P Localizer, CRS Wide, CLR Wide B Localizer, CRS NAR, CLR Wide C
Glide Slope Transmitter Configuration Code
Normal N Wide W Wide and CLR Demodulation B Narrow S Dephase Advance A Dephase Retard R Attenuate Middle Antenna M Attenuate Upper Antenna U Low Angle Alarm L High Angle Alarm H RF Power Alarm P Special Requirements Z Transverse Structure (FAF ALT) T Phase Verification Main Sideband Advance Phase PSA Phase Verification Main Sideband Retard Phase PSR Phase Verification Middle Antenna Advance Phase PMA Phase Verification Middle Antenna Retard Phase PM Waveguide Glide Slope Configuration Code
Main Sideband Advance MA Main Sideband Retard MR Upper Auxiliary Attenuate UZ Upper Auxiliary Advance UA Upper Auxiliary Retard UR Lower Auxiliary Attenuate LZ Upper and Lower Waveguide Advance ULA Upper and Lower Waveguide Retard ULR Main Waveguide Feed Advance FA Main Waveguide Feed Retard FR Lower Main Feed Attenuate LMZ Upper Main Feed Attenuate UMZ
(3) The remaining columns are intended for use as designated. They may be altered if necessary.
(4) Remarks/ Other Data. When manual mode is used to perform an inspection, enter the word "Non-AFIS" on the line preceding manual inspection entries.
(5) Best Fit Straight Line. Clearly state in Block 11 notes the runs used for BFSL reporting.
Suggested abbreviations to be used when completing this form:
RWY - Runway FREQ - Frequency CW - Commissioned or measured Course Width CAT - Category of ILS CE - Capture Effect NR - Null Reference SBR - Sideband Reference EH - Endfire Short ED - Endfire Standard EU - Endfire, Upslope Version WG - Waveguide ANGLE - Commissioned Glidepath GND TEMP - Ground Temperature OAT - Outside Air Temperature BARO - Barometric Altimeter Setting ALTITUDE - Altitude to Fly on ILS-2 PW - Path Width PA - Path Angle ALN - Alignment 190 μA - 190 Microamp Angle Mod - Modulation 90 Hz Sym - Symmetry of 90 Hertz side of width SBP - Structure Below Path Z1 - Localizer & Glide Slope Structure in Zone 1 Z2 - Localizer & Glide Slope Structure in Zone 2 Z3 - Localizer & Glide Slope Structure in Zone 3 Z4 - Localizer Structure in Zone 4 Z5 - Localizer Structure in Zone 5 POL - Polarization 150 CLR - Minimum localizer clearance on 150 Hz side of localizer 90 CLR - Minimum localizer clearance on 90 Hz side of localizer 2. FAA Form 8240-7-1, ILS Continuation Worksheet
a. Field 1 - Notes. Enter any additional information that may be useful in interpreting the results of the flight inspection.
b. Field 2. Complete as shown in FAA Form 8240-7, Paragraph 1l.
FLIGHT INSPECTION REPORT—ILS WORKSHEET
FAA FORM 8240-7
FLIGHT INSPECTION REPORT—ILS CONTINUATION WORKSHEET
Appx 7 - ILS Worksheet › ILS Continuation Sheet, 8240-7-1
FAA FORM 8240-7-1
APPENDIX 8. FLIGHT INSPECTION REPORT
INSTRUMENT LANDING SYSTEM
FAA FORM 8240-8 FAA Form 8240-8, Instrument Landing System, is designed to be used to report all the components or conditions of an instrument landing system (when necessary). This appendix provides guidelines for completing FAA Form 8240-8. For Transponder Landing Systems (TLS(s)), separate forms are required for each runway or separate approach procedure.
Appx 8 - ILS Report
NOTE: Commissionings of visual aids, NDB(s), and after accident reports on NDB(s) must be reported on FAA Form 8240-5. 1. Field 1 - Flight Inspection Report Header. Complete as shown in Chapter 2, Paragraph 12, except for the following:
a. Runway. Enter the applicable runway designator
b. Category. Enter the lowest minima performance category of the facility (I, II, III). 2. Field 2 - Crew Information – Complete as shown in Chapter 2, Paragraph 12. 3. Field 3 – Facility Information. Click on the drop-down box and select the appropriate option.
a. Localizer. Click on the drop-down box and select “Inspected,” “Required/ Not Inspected,” or if not required and not inspected, leave blank.
b. Offset. The Offset block refers to an offset localizer. Click on the drop-down box and select the appropriate entry in the localizer and in the offset block to indicate the item inspected was an offset localizer.
c. Glideslope. Click on the drop-down box and select “Inspected,” “Required/ Not Inspected,” or if not required and not inspected, leave blank.
d. LDA. Click on the drop-down box and select “Inspected,” “Required/ Not Inspected,” or if not required and not inspected, leave blank.
e. SDF. Click on the drop-down box and select “Inspected,” “Required/ Not Inspected,” or if not required and not inspected, leave blank.
f. TLS. For TLS facilities, if only part of the system is checked, Click on the drop-down box and select the appropriate entry in the TLS block and in the component checked (e.g., if only the glide slope was checked, select the appropriated entry in the TLS and glide slope blocks. If the whole system is checked, select an entry in the TLS block only).
g. Other*. Explain in Remarks.
h. DME. DME refers to any source of DME that may be required for the ILS approach. When the DME for an ILS approach is provided by a VOR/ DME, VORTAC, or TACAN, enter the identifier following the word "DME", and select the type facility providing the DME (e.g., BLV TAC). Click on the drop-down box and select the appropriate entry to indicate whether inspected and condition (i.e., “SAT” or “UNSAT*”).
i. Compass Locator. The "compass locators" block is used to report the condition of nondirectional beacons (NDBs) used as a part of an ILS system. If the identifier of the NDB is different from the ILS (compare the broadcast idents, not the AVNIS idents), enter the identifier after the words “compass locators”. If more than one NDB is a component of the ILS system, report the additional NDB(s) in the Remarks block. Click on the drop-down box and select the appropriate entry to indicate whether inspected and condition (i.e. “SAT” or “UNSAT*”).
j. Lighting System. . If all lighting features required to support the lowest authorized visibility are Satisfactory, mark accordingly. Click on the drop-down box and select the appropriate entry to indicate whether inspected and condition (i.e. “SAT” or “UNSAT*”).
k. 75 MHz Markers. See Chapter 3, Paragraph 21.
l. SIAP(s). Complete as directed in Chapter 3, Paragraph 21. Click on the drop-down box and select the appropriate entry to indicate whether inspected and condition (i.e. “SAT” or “UNSAT*”).
m. Publications. For publications checked IAW Order 8200.1, Paragraph 4.34f, click on the drop-down box and select the appropriate entry to indicate whether inspected and condition (i.e. “SAT” or “UNSAT*”).
n. Commissioned (Com’d) Width. Enter the tailored or standard course sector width.
o. Commissioned (Com'd) Angle. Enter the commissioned angle.
p. Glide Slope Type. Enter the type of glide slope being reported. Use the suggested abbreviations shown in Appendix 7, Paragraph 1l(4).
q. Facility Status (F/C, G/S, B/C). If inspected, click on the drop-down box and select the appropriate entry to indicate whether inspected and condition for the localizer front course (F/C), glide slope (G/S), and localizer back course (B/C).
r. ILS Classification System. The classification system is intended to provide a more comprehensive method of describing ILS performance than the currently used Facility Performance Category alone. A facility’s “Class” of performance is defined by using three characters. Flight inspection will report two of the three characters IAW Order 6750.24, Appendix 2. An excerpt from Order 6750.24 is provided as guidance for determining the appropriate character to enter in the ILS Classification System block.
(1) I, II, or III: As an example, an ILS that conforms to the ICAO Annex 10 Facility Performance CAT III standards, meets the CAT III localizer course structure criteria to ILS Point “D”, and conforms to the integrity and continuity of service objectives of Level 3, would be described as “Class IIID3”. An ILS, which conforms to ICAO Annex 10 Facility Performance CAT I standards, has a localizer CAT III course structure to Point “E”, and conforms to the integrity and continuity of service objectives of Level 2, would be described as “Class IE2”. However, when a CAT I facility performance is monitored to CAT II standards, this same facility having a localizer CAT III course structure to Point “E” and conforming to the integrity and continuity of service objectives to Level 2 would be described as “Class IIE2”. Conversion of a Facility’s Performance Class from CAT I to CAT II is dependent upon the facility performance being monitored to CAT II standards. When requested, IAW FAA Order 8400.13, Appendix 2, we are responsible for completing a flight check IAW the Flight Inspection Operations checklist contained therein. For our purposes, satisfactory results of all checklist items does not in and of itself constitute a reason to change the Facility’s Performance Class from a CAT I to a CAT II within the ILS Classification System block. A change of the Facility’s Performance Class will be dependent upon successful completion of all checklists contained in FAA Order 8400.13, Appendix 2, and publication of a “Special Authorization CAT II Operations to RVR 1600 or 1200” SIAP.
For tracking purposes, when the results of all Flight Inspection Operations checklist items are satisfactory, enter in Remarks, “This facility supports Facility Performance Class II”. Upon publication of the “Special Authorization CAT II Operations to RVR 1600 or 1200” SIAP, the Facility’s Performance Class within the “Performance Class” field on the AVNIS Facility Data Sheet will be changed by the FICO Aeronautical Information Specialist from CAT I to CAT II. On future reports, when the facility supports CAT II requirements, enter CAT II into the ILS Classification System block.
(2) A, B, C, T (Threshold), D, or E: This character defines the ILS point to which the localizer conforms to the Facility Performance CAT III course structure tolerances.
Enter the appropriate ILS Classification System characters in the block. Enter the Facility Performance Class (described in Paragraph 11a above) first, and the point to which the localizer conforms to the Facility Performance CAT III course structure tolerance (described in Paragraph 11b above) second. The 2nd character performance classification of “D” and “E” must be determined solely by rollout procedures. The low approach (50 ft) method may be used for subsequent classification if a comparability check was accomplished, found Satisfactory, and is documented on the AVNIS.
NOTE: If the rollout check has been accomplished and documented on the datasheet as “U4/ 5” or “Q4/ 5”, do not report a code inside Point T.
(a) Inspection Criteria. When the inspection is performed to a higher standard than the official category because it has been authorized IAW FAA Order 8400.13, Procedures for the Approval of Special Authorization Category II and Lowest Standard Category I Operations, and has a published “Special Authorization CAT II Operations to RVR 1600 or 1200” SIAP, enter the higher standard category. If the facility is not inspected to a higher standard, leave blank.
(b) Rollout. When rollout procedures are established IAW Order 8200.1 for any localizer, document the roll-out code. Click on the drop-down box and select the appropriate code. The available codes include:
1 S = Rollout accomplished; results of both the Rollout and the 50 ft run are within Category III tolerance and compare within 3 μA.
2 U4 = Rollout accomplished; Zone 4 results do not meet Category II/ III tolerances.
3 U5 = Rollout accomplished; Zone 5 results do not meet Category III tolerances.
4 R4 = Rollout required for evaluation of Zone 4 and Zone 5. Rollout was accomplished; ground results meet Category II/ III requirements but do not compare with results of the 50 ft run in Zone 4.
5 R5 = Rollout required only for evaluation of Zone 5. Rollout was accomplished; ground results meet Category III requirements; comparison with the 50 ft run was Satisfactory in Zone 4 but Unsatisfactory in Zone 5. 4. Field 4. - NOTAM(s). Complete NOTAM(s) block as directed in Chapter 3, Paragraph 21d. Restriction information on NDB(s) used only as Compass Locators must be reported. This restriction status must be entered in the Remarks section of the ILS AVNIS Facility Data Sheet.
5. Field 5. - Remarks. Complete as shown in Chapter 3. Additionally, when reporting localizer phasing (e.g. enter the start/ stop distance from the localizer antenna, the course sector side (90 Hz or 150 Hz), the offset from centerline (in degrees), and the MSL altitude flown).
a. 75 MHz Marker Beacon(s). See Chapter 3, Paragraph 21.
b. Clearance Below Path. When checking clearances to runway threshold on CAT I glide slopes with runway centerline localizers, explain in Field 13 (e.g., Clearance below path checked to Category II standards; results between Point C and Threshold are Satisfactory/ Unsatisfactory).
c. Localizer Course Width/Clearance Comparability (Procedure 1 or Procedure 2). When accomplished, document comparability check results on the AVNIS data sheet and the report (e.g. course width and clearance comparability verified from an altitude of 1,200 ft MSL up to 4,555 ft MSL, using procedure 1, IAW FAA Order 8200.1A, Paragraph 15.20k; or course width and clearance checks must be conducted at an altitude of 1,200 ft MSL). 6. Field 6 – Instrument Landing System Data- Azimuth (Part I). This field will be left blank when that component of the ILS is not inspected or reported on the same flight inspection form (i.e., do not enter "COM'D WIDTH" for the azimuth if the reported information is glide slope only, or vice versa). Enter the data for both the front and back courses in the appropriate transmitter (TX) column. If the localizer transmitter cannot be determined, indicate in Remarks.
a. ILS-1 Altitude. Enter the MSL altitude in feet at which the ILS-1 maneuvers were flown.
b. TX1/ TX2 CD (Code) Column. Under the appropriate transmitter number, click the drop-down box and enter the appropriate code. Enter an "X" for any out-of-tolerance condition found and not corrected during the inspection; enter a "C" for any out-oftolerance condition found and corrected during the inspection. Enter “SS” when structure is “SAT” per Order 8200.1, Paragraph 15.51a. Enter “CS” when clearance is “SAT” per Order 8200.1, Paragraph 15.51c. Do not enter an “X” or “C” for any out-of-tolerance found in Zone 4 and 5 on a CAT I localizer (Zone 5 for Category II localizer) when the structure is analyzed for the purpose of defining a facility’s “Class” of performance.
c. TX1/ TX2 Initial Column. Under the appropriate transmitter number, enter the "as found" operating condition in this column, if this condition was changed or altered during the inspection.
d. TX1/ TX2 Final Column. Under the appropriate transmitter number, enter the operating condition at the completion of the inspection. Use this column to report the results of after accident checks.
e. Course Width. Enter the measured, normal course sector width for each transmitter checked.
f. Symmetry. Enter the percent of symmetry of the 90 Hz side.
g. Modulation. Enter the "on course" modulation level in percent for each transmitter checked.
h. Clearance 150. Enter the minimum value in microamperes and the degrees from the course on the 150 Hz side (front or back) for each transmitter checked. An entry of 180/ 20.0 means the minimum clearance was 180 μA at 20° from the course. When a facility is restricted, enter the minimum clearance value found in the unrestricted area in Field 6. Also report the minimum clearance found within the restricted area in Field 5, except when restriction is based on terrain.
NOTE: Do not report the algebraic sign from the AFIS clearance readout.
For a TLS, indicate “S” for Satisfactory or “U” for Unsatisfactory. Explain Unsatisfactory conditions in Remarks. Clearance plots are not required.
i. Clearance 90. Enter the results found on the 90 Hz side as shown in Subparagraph 6h.
j. Course Structure - General Information. When a facility is restricted from a point in a zone, enter the maximum course displacement in the unrestricted portion of the zone in Field 9. Also report the maximum structure found within the restricted area in Remarks.
k. Course Structure - Z1, Z2, Z3, Z4, Z5. Report the maximum course displacement in microamperes due to roughness, scalloping, or bends for each transmitter checked. Report the course displacement for each zone and the distance from the threshold, antenna (back course), or missed approach point (e.g., 5/ 0.7 indicates the displacement was 5 μA at 0.7 nm). If distances are referenced to the MAP or antenna (back course), note in Remarks. When necessary to more accurately locate a structure value in a particular zone, report mileage to the nearest hundredth.
Zone 4 and 5 structure, which is analyzed for the purpose of defining a facility’s “Class” of performance must be reported unless restricted or the data sheet indicates a rollout code of “U4/ 5” or Q4/ 5”. Only the zones used to identify the normal “Category” of the system must be used to assign facility status. For inspections where Zone 4 and Zone 5 structure are evaluated both through roll-out and airborne (50 ft), report the roll-out results in this field and the airborne results in Remarks.
(1) When zones have tolerances which have linear rates of change, report the structure closest to the tolerance limit.
(2) Report the out of tolerance furthest from the threshold, antenna (back course), or missed approach point. Report additional out-of-tolerance structure closer to the threshold, antenna (back course), or missed approach in Remarks, if appropriate.
l. Vertical Polarization - Enter “S” if Satisfactory or “U” if Unsatisfactory. Explain Unsatisfactory conditions in Remarks.
m. Alignment. Enter the course displacement in microamperes, left or right of the designed course (e.g., 3R is 3 μA right of the course, “CL”, for no alignment error). LDA(s) oriented to a non-descript point-in-space, where adequate visual checkpoints are not available and AFIS runway updates are impractical, must be reported either Satisfactory (S) or Unsatisfactory (U).
n. Identification. Enter "S" if Satisfactory or "U" if Unsatisfactory.
o. Power Ratio. Enter the power ratio value in dB.
p. Localizer Only Structure. Report localizer only approach final segment maximum structure. Report the structure closest to the tolerance limit (e.g., localizer only structure 14/ 0.4 miles). 7. Field 7 - Instrument Landing System Data – Glide Slope (Part I)). Columns are provided for each transmitter and are labeled similar to the localizer entries. This field must be left blank when that component of the ILS is not inspected or reported on the same flight inspection form (i.e., do not enter “COMD ANGLE” for the glideslope if the reported information is localizer only, or vice versa). Enter the data in the appropriate (TX) column. If the glidelope transmitter cannot be determined, indicate in Remarks.
a. ILS-2 Altitude. Enter the altitude in feet MSL at which the ILS-2 maneuvers were flown.
b. TX1/ TX2 CD Column. Under the appropriate transmitter number, enter an “X” for any out-of-tolerance condition found and not corrected during the inspection; enter a “C” for any out-of-tolerance condition found and corrected during the inspection. Enter “SS” when structure is “SAT” per Order 8200.1, Paragraph 15.51a.
c. TX1/ TX2 Initial Column. Under the appropriate transmitter number, enter the “as found” operating condition in this column, if this condition was changed or altered during the inspection.
d. TX1/ TX2 Final Column. Under the appropriate transmitter number, enter the operating condition at the completion of the inspection. Use this column to report the results of after accident checks.
e. Angle. Enter the measured, actual glidepath angle. If the reported angle is not the actual angle, explain in Remarks.
f. Modulation. Enter the modulation level in percent.
g. Width. Enter the width of the normal glidepath envelope, as measured on a level run.
h. Structure Below Path. Enter the normal level run angle where 190 μA of fly-up signal occurs.
i. Symmetry. Enter the percent of symmetry of the 90 Hz side.
j. Path Structure - General Information. If a facility is restricted from a point in a zone, enter the maximum on-path displacement in the unrestricted portion of the zone in this field.
k. Path Structure Z1, Z2, Z3. Report the maximum on-path displacement in microamperes due to roughness, scalloping, or bends for each transmitter checked. Report the path displacement for each zone and the distance from the threshold (e.g., 5/ 0.7 indicates the displacement was 5 μA at 0.7 nm). If it is necessary to more accurately identify structure in a particular zone, report mileage to the nearest hundredth. Due to flight inspection limitations of the Sierra AFIS system, manual analysis of Z3 glide slope structure is required.
(1) When zones have tolerances that have linear rates of change, report the structure closest to the tolerance limit.
(2) Report the out of tolerance furthest from the threshold. Report additional out-of-tolerance structure closer to the threshold in Remarks, if appropriate.
Continue reading ↓ 120 of 181 passages shown