HANDOUTS (HO) & PRACTICE EXERCISES (PE)



Handouts (HO) & Practice Exercises (PE)

Table of Contents:

HO-01-PVF Steps for Certificating an Operator: 5-Phase Test Process (Part 135/91K) 3

HO-02-PVF Steps for Certificating an Operator: 4-Phase Test Process (Part 121) 5

HO-03-PVF General Purpose Proving and Validation Test Job Aid (Part 135/91K) 7

HO-04-PVF NextGen Tracking Tool 11

HO-05-PVF Special Areas of Operation Requiring Input from Specialist 39

HO-06-PVF Oceanic and International Operations Manual Checklist 41

This page intentionally left blank.

HO-01-PVF Steps for Certificating an Operator: 5-Phase Test Process (Part 135/91K)

[pic]

The Five Phases of Certification and Requirements of the Gate System for Part 135

[pic]

HO-02-PVF Steps for Certificating an Operator: 4-Phase Test Process (Part 121)

[pic]

Phases and Gates for Initial Certification For Part 121

The Four Phases of the Certification Process and the Gate System for the initial Certification of Part 121 Air Carriers

[pic]

HO-03-PVF General Purpose Proving and Validation Test Job Aid

(Part 135/91K)

|Operator/Program Manager Official Name/Cert. Number: |

|PHASE ONE: REQUEST FOR AUTHORIZATION |

|PTRS/DCT CODE | |INSP.’S INITIAL |DATE REC’D |DATE ACCEP’D |NOTES |

| |Initial Contact Meeting | | | | |

| |Determine need for proving and/or | | | | |

| |validation testing | | | | |

| |Applicant advised of applicable guidance,| | | | |

| |to include this job aid | | | | |

| |Assign FAA Test Team | | | | |

| |Internal FAA Coordination | | | | |

| |Open master PTRS Record | | | | |

| |#_____________________ | | | | |

| |ATOS Data Collection Tool (DCT) (as | | | | |

| |applicable) | | | | |

| | | | | | |

|PHASE TWO: PROVING/VALIDATION TEST PLAN |

|PTRS/DCT CODE | |INSP.’S INITIAL |DATE REC’D |DATE ACCEP’D |NOTES |

| |Identification of company coordinator | | | | |

| |Detailed schedule of all proposed flights | | | | |

| |List of names & positions of flight crew| | | | |

| |members on each flight | | | | |

| |Names, titles & company affiliation of all| | | | |

| |non-crew members on each flight | | | | |

| |Applicants plan for reducing test hours | | | | |

| |(if applicable) | | | | |

| |FAA Test Team Leader initial review of | | | | |

| |test plan | | | | |

| |Update master PTRS record | | | | |

| |ATOS DCT (as applicable) | | | | |

| | | | | | |

| | | | | | |

| | | | | | |

| | | | | | |

| | | | | | |

| | | | | | |

| | | | | | |

| | | | | | |

| | | | | | |

|PHASE THREE. FAA TEST TEAM PLAN REVIEW |

|PTRS/DCT CODE | |INSP.’S INITIAL |DATE REC’D |DATE ACCEP’D |NOTES |

| |Manuals/Procedures (as applicable): | | | | |

| |General Operations Manual (GOM) or Program| | | | |

| |Operating Manual (POM) | | | | |

| |General Maintenance Manual (GMM) | | | | |

| |Maintenance Technical Manuals | | | | |

| |Cockpit Normal/Abnormal/Emergency | | | | |

| |Checklists and Procedures | | | | |

| |FAA Approved Flight Manual (AFM) | | | | |

| |Flight Attendant Manual | | | | |

| |Company Emergency Manual | | | | |

| |Passenger Briefing Cards | | | | |

| |Aircraft Fueling | | | | |

| |International Operations | | | | |

| |Dispatch/Flight Following/Flight Locating | | | | |

| |Weight & Balance | | | | |

| |Hazardous Material Recognition and/or | | | | |

| |Acceptance | | | | |

| |MEL/CDL | | | | |

| |Flight Planning | | | | |

| |Deicing/Anti-Icing | | | | |

| |Carry-On Baggage | | | | |

| |Exit Seating | | | | |

| |Aircraft cargo loading manuals and | | | | |

| |specific cargo handling manuals | | | | |

| |Station Operations Manual | | | | |

| |Enhanced Weather Information Systems | | | | |

| |(EWINS) | | | | |

| |Training Manuals/Programs/Procedures (as | | | | |

| |applicable): | | | | |

| |Flight crew Training | | | | |

| |Flight Attendant Training | | | | |

| |Dispatch/Flight Following/Flight Locating | | | | |

| |Training | | | | |

| |Maintenance Training | | | | |

| |Ground Personnel | | | | |

| |Destination/Alternate Airport Analysis | | | | |

| |Other Inspections/Reviews (as applicable):| | | | |

| |Aircraft Conformity | | | | |

| |Operational Control (Lease Agreements & | | | | |

| |DBAs) | | | | |

| |Cargo Evaluations | | | | |

| |Service/Contract Agreements | | | | |

| |Environmental Assessment | | | | |

| |Exemption/Deviation/Waiver Requests | | | | |

| |Weight and Balance Training | | | | |

| |Cargo Loading and Handling Training | | | | |

| |Ground Handling Procedures Training (if | | | | |

| |new aircraft or station) | | | | |

| |Emergency Evacuation Demonstration Plan | | | | |

| |(as applicable) | | | | |

| |Ditching Demonstration Plan (as | | | | |

| |applicable) | | | | |

| |Notify RFSD of proving/validation flight | | | | |

| |dates, times, locations, etc. | | | | |

| |Make Test Team member assignments | | | | |

| |Coordinate with TSA re: Security | | | | |

| |procedures and training | | | | |

| |Coordinate with FAA Hazmat Division | | | | |

| |Ensure Administrative requirements e.g. | | | | |

| |passport, visa’s, country clearance(s) | | | | |

| |Issue Draft OpSpecs/MSpecs | | | | |

| |LOA (if required) | | | | |

| |Update master PTRS record | | | | |

| |ATOS DCT (as applicable) | | | | |

|NOTE: During initial air operator certification or program manager authorization, the above manuals/programs may have already been reviewed. |

| |

|PHASE FOUR: INSPECTION AND DEMONSTRATION |

|PTRS/DCT CODE | |INSP.’S INITIAL |DATE OBJECTIVEACHIEVED |NOTES |

| |Order to Show Cause from DOT (part 121 | | | |

| |applicants) | | | |

| |Emergency Evacuation Demonstration (as | | | |

| |applicable) | | | |

| |Ditching Demonstration (as applicable) | | | |

| |Proving and/or Validation Flight | | | |

| |Table-top demonstrations | | | |

| |Flight Preparation | | | |

| |Pre-flight | | | |

| |En Route | | | |

| |Post- Flight | | | |

| |Applicant Record Keeping | | | |

| |Validation Testing | | | |

| |Table-top demonstrations | | | |

| |In-depth review of: | | | |

| |Applicant’s proposed procedures | | | |

| |Training Programs | | | |

| |Manuals | | | |

| |Facilities | | | |

| |Maintenance Programs | | | |

| |Update Master PTRS record | | | |

| |ATOS DCT (as appropriate) | | | |

| | | | | |

|PHASE FIVE: APPROVAL/DISAPPROVAL |

|PTRS/DCT CODE | |INSP.’S INITIAL |DATE |NOTES |

| |Final Economic Authority (DOT) (If | | | |

| |applicable) | | | |

| |PI Approve/Issue OpSpecs/MSpecs | | | |

| |Letter of Disapproval (if applicable) | | | |

| |Test Team – Complete individual PTRS | | | |

| |records | | | |

| |CPM complete/close Master PTRS record | | | |

| |CPM complete/close ATOS Data Collection | | | |

| |Tool (DCT) (as applicable) | | | |

HO-04-PVF NextGen Tracking Tool

NEXTGEN APPLICATION TRACKING TOOL INSTRUCTION GUIDE:

General Guidance:

The NextGen Application Tracking SharePoint is a site designed to increase the efficiency of all NextGen application processing. It allows for instantaneous notification to approving authorities as well as provides automatic tracking for routing history. Additionally, the NextGen Application Tracking SharePoint creates a paperless process.

Guidance from the 8900.1 Volume 3, Chapter 1:

From Paragraph 3-1:

1 Tracking Operational Applications. The Federal Aviation Administration (FAA) principal inspector (PI) will provide a written status report at certain milestones to applicants for the Next Generation Air Transportation System (NextGen) operational and non-standard operation specification, management specification, and letter of agreement (OpSpec/MSpec/LOA) approvals that require Flight Standards Service (AFS) Regional Office (RO) and/or headquarters (HQ) level concurrence. Examples include Required Navigation Performance/special aircraft and aircrew authorization required (RNP/SAAAR), Category II/III (CAT II/III) Approach, etc. At a minimum, provide the following updates:

• Monthly (or 30 days);

• Upon receipt of an application package at regional and HQ levels;

• Upon providing final decision; and

• Within 3 days of a request for status by the applicant.

2 Online Posting. The FAA PI who receives the application will upload an electronic version of the application to the NextGen Application Tracking SharePoint site associated with his or her region, and provide status updates to the applicant as noted above in subparagraph D. Additionally, this PI will be the individual responsible for providing the applicant with the status updates.

From Paragraph 3-3:

N The FAA PI who received the NextGen operational approval or non-standard OpSpec/MSpec/LOA/Tspec application, will upload an electronic version of the application to the NextGen Application SharePoint site, when approved for review. The PI will upload the application for their region as listed below:

• Alaskan Region (AAL): ;

• Central Region (ACE): ;

• Eastern Region (AEA): ;

• Great Lakes Region (AGL): ;

• Northwest Mountain Region (ANM): ;

• Southern Region (ASO): ;

• Southwest Region (ASW): ; and

• Western-Pacific Region (AWP):

Step-by-Step Instructions:

The following is a step by step instruction for the usage of the NextGen Application Tracking site. Of note, all red-starred items are required information.

1) The above links will take you to the appropriate NextGen Application Tracking site. Once there, click on “New Item.”

[pic]

2) Enter in the correct date for submission using the calendar.

[pic]

3) Attach any documentation by clicking on “Attach File.”

[pic]

a. Click “Browse”

[pic]

b. Select the appropriate document and click “Open.”

[pic]

c. Click “OK.”

[pic]

4) “Send Email” will default to “Yes.” “Yes” ensures the e-mail notification is sent to the address entered into the “Forward To” box.

[pic]

5) Select the appropriate “Forward To” from the drop-down box. For field offices, this will be the appropriate Regional NextGen branch. For the Regional Branches, this will be the Headquarters if it requires headquarters’ review.

[pic]

6) Enter a CC address as needed. This will send an e-mail notification to this address as well as the one in the “Forward To” box.

[pic]

7) Enter comments as necessary (i.e., any pertinent information regarding the application).

[pic]

8) Enter the Application Title.

[pic]

9) Choose the appropriate Application Type from the drop-down box.

[pic]

10) Enter a Control Number (if applicable).

[pic]

11) Enter the Initiator’s Name and e-mail address (this is normally the PI’s information).

[pic]

12) Select the appropriate Initiating Region from the drop-down box.

[pic]

13) Enter the Operator’s Name, e-mail address, and Telephone Number.

[pic]

14) Enter date for Last Application Update. (Note: When initiating the application, this date should match the initiation date; however, each update (per 8900.1 Volume 3, Chapter 1) should be noted with this calendar.)

[pic]

15) Review the Routing History. (Note: For initial entries, this will be blank. Once the application is sent, this box will automatically record the chronological routing history.)

[pic]

16) Select a completion date from the Process Complete calendar only when final approval has been given to the operator.

[pic]

17) Note the attachment linked at the bottom of the form.

[pic]

18) Click “Save and Close.” Once saved, the tracker will automatically send e-mail notifications to the addresses entered into the document.

[pic]

19) The Application Library will now look like this. Note that the tracker automatically populates the “Next Application Update” field with a default of 30 days, per 8900.1 Volume 3, Chapter 1 guidance.

[pic]

20) When editing is required, place the mouse arrow over the “down arrow” next to the document title and click. From the drop-down menu, select “Edit Item.”

[pic]

21) Make the appropriate edits. Select “Save and Close” when edits are complete.

[pic]

22) Once the process is complete, edit the document, and select the completion date from the “Process Complete” calendar at the bottom of the application.

[pic]

23) Select “Save and Close.” The process is now complete and the Application Library will now look like this (note the “Process Complete” date to the left of the application title).

[pic]

HO-05-PVF Special Areas of Operation Requiring Input from Specialist

Note: This table is not listed in FAA Order 8900.1, but it is a good reference for determining involvement of a specialist based on the operator’s request for a particular OpsSpec.

|OpSpec |Description |Primary Specialist |Supporting Specialist |

|A056 |Data-Link (CPDLC and ADS-C) |Navigation |Avionics/Dispatch |

|A353A153 |ADS-B |Navigation |Avionics/Dispatch |

|B034 |PRNAV/BRNAV |Navigation |Avionics/Dispatch |

|B036 |Class II Navigation-Multiple LRNS |Navigation |Avionics/Dispatch |

|B037 |CEP |Navigation |Dispatch |

|B038 |NOPAC |Navigation |Dispatch |

|B039 |NAT MNPS |Navigation |Dispatch |

|B040 |AMU |Navigation |Dispatch |

|B041 |Twin Eng NAT Ops |Navigation |Dispatch |

|B043 |Special Fuel Reserves |Dispatch |Navigation |

|B343 |Special Fuel Reserves |Dispatch |Navigation |

|B044 |Planned Re-dispatch/Re-release |Dispatch |Navigation |

|B046 |RVSM |Maintenance |Avionics/Dispatch |

|B050 |China |Navigation |Dispatch |

|B050 |Russia |Navigation |Dispatch |

|B050 |WATRS |Navigation |Dispatch |

|B050 |Gulf of Mexico |Navigation |Dispatch |

|B054 |Class II Navigation-Single LRNS |Navigation |Avionics/Dispatch |

|B055 |Polar |Navigation |Dispatch |

|B059 |Canadian MNPS |Navigation |Dispatch |

|B342 |ETOPS |Maintenance |Dispatch/Navigation |

|B344 |ETOPS |Maintenance |Dispatch/Navigation |

|Future special sensitive areas or B050 guidance requiring |Navigation |Avionics/Dispatch |

|specialized procedures | | |

This page intentionally left blank.

HO-06-PVF Oceanic and International Operations Manual Checklist

This page intentionally left blank.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download