08.01.2015 Views

BY ORDER OF THE SECRETARY OF THE AIR FORCE AIR FORCE ...

BY ORDER OF THE SECRETARY OF THE AIR FORCE AIR FORCE ...

BY ORDER OF THE SECRETARY OF THE AIR FORCE AIR FORCE ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AFMAN 11-217V1 3 JANUARY 2005 191<br />

8.8.5.5.2. Your call sign.<br />

8.8.5.5.3. Your aircraft type in terms the average VFR pilot will understand.<br />

8.8.5.5.4. Your location in terms the average VFR pilot will understand.<br />

8.8.5.5.5. Your intentions.<br />

8.8.5.5.6. Repeat the name of the airport.<br />

8.9. Flyability Checks.<br />

8.8.5.5.6.1. Example: “Shenandoah traffic, Track 66, white Learjet, 5 miles<br />

south on the straight-in ILS Runway 5, touch and go, Shenandoah.”<br />

8.9.1. Instrument procedure flyability checks are flown to ensure procedures are safe,<br />

practical, and consistent with good operating procedures before general use. They may<br />

be accomplished in lieu of or in addition to an official flight check. Whenever possible,<br />

flyability checks should be conducted by instructor/evaluator pilots. Flyability checks<br />

are NOT official flight inspections (“flight checks”), but shall include the entire<br />

procedure including the missed approach segment and all holding patterns. Prior to<br />

accomplishing a flyability check, pilots will review applicable portions of AFI 11-230,<br />

Instrument Procedure.<br />

8.10. Procedure and Database Problem Reporting.<br />

8.10.1. Despite the best quality control measures, it is still possible for aircrews to<br />

discover errors in databases, instrument procedures, charts, etc. If you discover a<br />

discrepancy or a discrepancy between two sources (ex. procedure pulled from aircraft<br />

database differs from paper IAP), report the discrepancy to your unit<br />

Standardization/Evaluation function. They, in turn, should report the details to the source<br />

of the database or procedure. All sources of databases, instrument procedures, charts, etc.<br />

have established procedures for reporting errors. Procedures and points of contact vary<br />

by vendor and organization and are located in the documentation that comes with the<br />

particular product.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!