# Presentation: 531203

## 14 CFR Part 135 Seminars

**Operations Considerations**

## Topics

**Operations Specification (OPSS) Para. C063**
**New Flight Plan Suffixes**
**Documentation**
- Duty Hours (incl. transportation, ex. Base1-Base2)
- Differences Training and Checking
- Seat-Dependent Training and Checking
- PRIA surveillance
**Discussions For the Good of the Group**

## Operations Specifications (OPSS) Paragraph C063 – Old

_**Published RNAV Instrument Approach Operations Using an Area Navigation System;**_** HQ Revision:  01x**
- Old paragraph (prior to October 2005)
- Listed aircraft (M/M/S), RNAV system (Manufacturer/Model)
- Required training and checking
- Required COMPANY high mins. (1st 6 months:  Add 200 ft; 1⁄2 sm)
- Now only found in guidance for OPSS paragraph C052
- Authorizations include:
- Col. 1; Non-precision _without_ vertical guidance:  GPS, RNAV (GPS)
- RNAV (RNP) authorized by OPSS paragraph C384
- Col. 2; Non-precision _with_ vert. guid.:  RNAV (GPS), RNAV (GNSS)
- Use of vertical guidance authorized by OPSS paragraph C073
- Still requires training and checking
- Originally by HBAT 95-02A

## Operations Specifications (OPSS) Paragraph C063 – New

_**IFR RNAV Departure Procedures (DP) and Standard  Terminal Arrivals (STAR);**_** HQ Control:  10/12/05; HQ Revision:  02a**** **
- New paragraph (effective October 2005)
- Lists aircraft M/M/S, RNAV system (Manufacturer/Model), RNAV procedures (Types A & B and Q routes), Limitations/Provisions
- Approved training for each flight crewmember
- Flight crew must verify system for each planned operation
- An indicator must be visible when system performance is insufficient for ATC accuracy
- Q routes authorized
- If Type B qualified
- If Type A qualified; must have IFR-approved GPS
- RNAV DP’s and STAR’s
- Designated as Type A or Type B
- Information found in AC 90-100 and the AIM

## Operations Specifications (OPSS) Paragraph C063 – NewSample Data Required

| Airplane 
M/M/S | Area Navigation System |  | RNAV DPs/STARs
Type A and/or Type B 
Q Routes | Limitations and Provisions |
| --- | --- | --- | --- | --- |
|  | Manufacturer | Model |  |  |
| Aircraft Make and Model | Garmin | GNS-530 & GNS-430 | Type B, Type A, and Q-Route RNAV (GPS or DME/DME/IRU + or - 1NM) | According to AFM and AFM Supplement |
| Aircraft Make and Model | Collins | FMS-6000 with GPS-4000(X) | Type B, Type A, and Q-Route RNAV (GPS or DME/DME/IRU + or - 1NM) | According to AFM and AFM Supplement.  DME/DME or DME/DME/DME IRU is not  approved |

## Operations Specifications (OPSS) Paragraph C063 – New

**Chart Notes required:**
- Type A procedures
- Type A
- DME/DME, DME/DME/IRU, or GPS required
- Pilots of RNP-capable aircraft, use RNP-2.0
- Type B procedures
- Type B
- DME/DME/IRU or GPS required
- Pilots of RNP-capable aircraft, use RNP-1.0 *(or RNP-2.0)*
*Some may require GPS and will note: “GPS required”*

## Operations Specifications (OPSS) Paragraph C063 – New

**Operational characteristics**
- Type A
- RNAV inputs described (see previous slide)
- Pilots _encouraged_ to use CDI, FD, and/or A/P in lateral nav mode
- DP:  Start as low as 2000’ above airport
- Type B
- RNAV inputs...
- Pilots _must_ use CDI, FD, and/or A/P in lateral nav mode
- DP:  aircraft without GPS-must ensure nav system position within 1000 feet at start point of TO roll (runway update OK)
- DP:  Start as low as 500’ above airport

## Operations Specifications (OPSS) Paragraph C063 – New

**14 CFR Part 91 operators MUST be authorized, too!**
**FYI**
- OPSS paragraphs (instead of LOA’s) are now issued to Part 91 operators for:
- ADS-B, CPDLC
- B-RNAV, P-RNAV, RNP
- RVSM, NAT/MNPS
- CAT II and CAT III operations
- RNAV SID’s and STAR’s (C063)
- MMEL use for MEL
- Other operations that required an LOA
- LOA expires; OPSS does not

## Revised Aircraft Equipment Suffixfor FAA Flight Plans (effective Sep 01, 2005)

|  | NO DME |
| --- | --- |
| /X  | No transponder  |
| /T  | Transponder with no Mode C  |
| /U  | Transponder with Mode C  |
|  | DME |
| /D  | No transponder  |
| /B  | Transponder with no Mode C  |
| /A  | Transponder with Mode C  |
|  | TACAN ONLY |
| /M  | No transponder  |
| /N  | Transponder with no Mode C  |
| /P  | Transponder with Mode C  |

|  | AREA NAVIGATION (RNAV) |
| --- | --- |
| /Y  | LORAN, VOR/DME, or INS with no transponder  |
| /C  | LORAN, VOR/DME, or INS, transponder with no Mode C  |
| /I  | LORAN, VOR/DME, or INS, transponder with Mode C  |
|  | ADVANCED RNAV WITH TRANSPONDER AND MODE C (If an aircraft is unable to operate with a transponder and/or Mode C, it will revert to the appropriate code listed above under Area Navigation.) |
| /E  | Flight Management System (FMS) with DME/DME and IRU position updating |
| /F  | Flight Management System (FMS) with DME/DME position updating |
| /G  | Global Navigation Satellite System (GNSS), including GPS or WAAS, with enroute and terminal capability.   |
| /R  | Required Navigational Performance.   The aircraft meets the RNP type prescribed for the route segment(s), route(s) and/or area concerned. |

|  | Reduced Vertical Separation Minimum (RVSM).  Prior to conducting RVSM operations within the U.S., the operator must obtain authorization from the FAA or from the responsible authority, as appropriate. |
| --- | --- |
| /J | /E with RVSM  |
| /K | /F with RVSM  |
| /L | /G with RVSM  |
| /Q  | /R with RVSM  |
| /W  | RVSM |

## Documentation

**Duty hours include more than just arriving at the airport for flight duty until flight ends**
- Moving from one base to another to get to a different aircraft than usual counts for duty...
- Office time – usually a manager concern, but can be for others

## Documentation

**Training and Checking requirements**
- Differences
- CE-500, CE-501, CE-550, CE-560
- LR-24, LR-25, LR-35
- PA-28-161, PA-32-300, CE-172...
**!!!  Same aircraft type (LR-35) – Different avionics !!!**
- Seat-Dependent
- HBAT 95-13
- PIC who sits in right seat **OR** SIC who sits in left seat
- Includes company Instructors and Check Airmen
- Identify PF and PNF tasks and procedures (Takeoff roll)
- Identify control systems (FMS, nav, autopilot, etc.)
- Identify operational procedures or job functions (Cat II ops)
- Identify controls and/or displays not common (Switch not reachable)
- Document, rate level of training & currency required
- Develop training program for POI approval

## Documentation

**FAA records by regulation...14 CFR 135.63**
- Pilot (& Flight Attendant) records – 1 year
- Trip records (Load manifests) – 30 days
- Current aircraft list – 6 months
**Pilot Records Improvement Act (PRIA)**
- Share pilot information with other operators
- You must ask for your new hires
- You must give for others’ who hire
- 5-year history
- Required sharing (asking and telling) to be documented
- Must be inspected by FAA for compliance