My apologies, somehow the 2nd half of the text was cut off. Here is the full text:
Pan-Pacific UAS Test Range Complex
Flight Planning Guide
Purpose
The
purpose of this flight planning guide (FPG) is to identify information
regarding the proposed operation and control of a specific UAS in the Test
Range. While the capability to execute UAS operations is must be flexible
enough to recognize that each system, sub-system, ancillary piece of equipment,
and their required readiness procedures are different, there are several basic
flight safety provisions that must be followed.
This
FPG will remain a “living guide” regarding the operation of each system in that
it is recognized that there are presently no standard FAA approved FPG
procedures for any UAS which ensure that UAS flight operations are conducted in
a safe manner and in accordance with operating procedures established by the
Test Site and the FAA. This FPG will set forth procedures designed to identify
system capabilities & vulnerabilities and verify that adequate safeguards
exist to protect against the National Airspace System (NAS)
Because
of the nature of UAS being relatively new to aviation, the uniqueness of each
vehicle and mission is designed such that this document will undergo continuous
changes as it adapts to both the NAS and the individual system needs.
Instructions
An
FPG will serve as the Mission Planning Guide as it is designed to adhere to
each systems limitations and capabilities as it administers changes to the
NAS. The FPG will be developed for each
mission and will be submitted to the FAA NLT 30 days prior to each mission
date.
The
Mission Commander shall ensure the FPG is developed in concurrence with all
applicable FAA rules and regulations.
As
subsequent missions are performed and the FPG develops further, subsequent
versions will be submitted to the FAA as they evolve. Changes to the FPG will be documented in a
cover letter as each subsequent version is submitted.
Required
Information
1.
Mission: Provide a brief
overview of the UAS mission(s) and capabilities.
1.1.
Objectives
1.2.
Description
1.3.
Explain
whether the proposed test will, or is expected to, exceed limitations used to predict
mean time between failure or other safety models.
1.4.
Develop
then provide fault trees and/or failure mode effects analysis.
1.5.
Capabilities
2.
Vehicle
2.1.
User
Handbook –
2.1.1.
Is
UAS user handbook available? Please attach.
2.1.2.
Is sub-system user handbook available? Attach
2.1.3.
Is Ancillary system user handbook available? Attach
2.2.
Physical
Characteristics
2.2.1.
Measurements
- wingspan, fuselage length, body diameter
2.2.2.
Composition
2.2.3.
Weight
- empty and max load
2.2.4.
Fuel
- type and capacity
2.2.5.
Landing
style/type
2.3.
Propulsion
System
2.3.1.
Engines
–
2.3.1.1.
type,
2.3.1.2.
number,
2.3.1.3.
manufacturer,
2.3.1.4.
horsepower
rating,
2.3.1.5.
electrical
power source
2.3.2.
Fuel
Volume and Consumption Monitors
2.3.3.
Limitations
and Failure Modes
2.3.3.1.
By
environmental conditions (temperature, icing, dust)
2.3.3.2.
Confirmed
by test data
2.3.3.3.
Considered in test plan
2.4.
Performance Characteristics
2.4.1.
Performance Charts
2.4.2.
Takeoff and Landing
2.4.2.1.
Distances for maximum weights
2.4.2.2.
Maximum crosswind tolerance
2.4.3.
Maximum Altitude
2.4.4.
Maximum Endurance
2.4.5.
Maximum Range
2.4.6.
Range vs. Altitude (Comm Link)
2.4.7.
Airspeed –
2.4.7.1.
cruising,
2.4.7.2.
maximum,
2.4.7.3.
minimum
2.4.7.4.
stall
2.4.8.
Rate of Climb (degrees)
2.4.9.
Rate of Descent (degrees)
2.4.10.
Weather Minimums (?)
2.4.10.1.
Clouds
2.4.10.2.
Instrument Flight Rules (IFR) conditions
2.5.
Flight Reference Data
2.5.1.
On-board sources of position, altitude, heading, altitude, and
airspeed information to the UAS operator or autopilot
2.5.2.
Backups
2.6.
Transponder - Does the UAS have an on-board transponder with
Mode C altitude reporting?
2.7.
ADS-B?
2.8.
TCAS?
2.9.
Payload Options - What payload(s) will be used on the UAS
during operations?
2.10.
Hazardous Materials - List
all materials that require special handling, such as flammable, toxic, energy
storage, or ordinance. Include flight termination system if applicable.
3.
Command and Control Systems: Brief
paragraph that describes the systems/methods used to control the UAS during
flight; include frequencies where appropriate.
3.1.
Control Method - primary and secondary
3.2.
Satellite or Line of Sight
3.3.
Frequency Allocation - Is there a frequency allocation for all
RF links? On what frequencies do the UAS systems operate? What is the effect of
radio frequency interference on the command and control system?
3.4.
Command Link Range - What is demonstrated range of primary command
and control (C2) transmitter and receiver
3.5.
Backup –
3.5.1.
Is there a backup C2 transmitter and receiver?
3.5.2.
Does the backup have the same effective
radiated power?
3.5.3.
Is the backup link sufficiently
protected from spurious command signals?
3.6.
Link Analysis
3.6.1.
Briefly explain how RF link analysis was
performed to verify that both primary and backup transmitters can communicate
with vehicle at furthest point of planned operation?
3.6.2.
Does link analysis address all RF links?
3.6.2.1.
Uplinks from primary and backup ground stations
3.6.2.2.
Secondary uplinks from each
ground station
3.6.2.3.
Downlinks to primary and backup ground stations
3.6.2.4.
Flight termination link
3.6.2.4.1.
Is there at least 12 dB of signal excess
in FTS link?
3.6.2.4.2.
Explain how it was determined that the
vehicle primary and backup command and control receivers and FTS receivers are
operating at specified sensitivity?
3.6.3.
Did our link analysis consider the RF
horizon?
3.6.4.
What is the maximum range for each link?
3.6.4.1.
List each link separately here
3.6.5.
Briefly explain how we determine if the
primary and backup transmitters are radiating manufacturers specified output
power?
3.6.6.
Frequency Masking
3.6.6.1.
Are there any nulls in the C2
transmitter antenna pattern?
3.6.6.2.
Are there areas of RF masking due to
location of antennas on the UAS relative to their position and to ground
station antennas? (during turns or pitch?)
3.6.6.3.
Are there any RF null spots in the C2
link based on the position or orientation of the UAS relative to the control
station?
3.6.6.4.
Do the operators know where these nulls
are and have mission profiles been designed to avoid these nulls?
3.6.7.
Multipath –
3.6.7.1.
What is the link susceptibility to
multipath?
3.6.7.2.
What is the system response if multipath
is experienced?
3.7.
Takeoff and Landing - What is method?
3.8. Navigation System - What is the source of navigation
information for the operator? Are there redundant sources?
4.
Operations
4.1.
Crew
4.1.1.
Requirements - Please list the total number of personnel
involved in the mission and their associated job functions.
4.1.2.
Experience - Detail the crew’s flight qualifications,
experience, and currency with this UAS. How recently did each crewmember fly
this type of UAS?
4.1.3.
Safety - What information does the crew have to make safety
related decisions?
4.2.
Pre-Flight
4.2.1.
Set-up Time - Upon arrival, how much set-up time is required to
prepare for initial flight?
4.2.2.
Pre-Flight Checks -- Describe typical ground checks for the UAS
and control system.
4.3.
Launch - Please describe the takeoff procedure and handoff
method in detail.
4.4.
Recovery - Please describe the recovery and landing procedure
in detail.
4.5. Turnaround Time - Describe any required post-flight maintenance
and the turnaround time between missions.
5.
Failure (Risk) Management
5.1.
Safety History
5.1.1.
Flight history
5.1.1.1.
Estimated total system hours based on this UAS
5.1.1.2.
Approximate hours logged by all PPUTRC operators
5.1.2.
Mishap history - List
the mishap history of the UAS
5.1.2.1.
Identify for the record
major failure modes.
5.1.2.2.
List known system-fault
crashes or failures have occurred with this UAS?
5.1.2.3.
List known system-fault
crashes or failures have occurred while a test system
5.1.2.4.
List crashes or
failures attributed to human error
5.1.3.
Corrective actions taken to correct for past mishaps, crashes or
failures
5.1.3.1.
Corrective actions implemented to circumvent any known system-fault
crashes or failures
5.1.3.2.
Corrective actions implemented to circumvent any human error
caused crashes or failures
5.2.
Demonstrated Reliability
5.2.1.
Estimated time between equipment failures
5.2.1.1.
Calculated from analytical or empirical data
5.2.1.2.
Environmental and performance limitations used to estimate
reliability figures
5.3.
Hazard Analyses –derived from overall Safety Review of system vs.
mission
5.4.
Software
5.4.1.
Explain how we implement and ensure our software safety program
5.4.2.
Software controlled components - What flight critical
components are software controlled?
5.4.3.
Analyses - Have any software safety analyses been performed?
5.5.
Loss of Command and Control (C2) Link
5.5.1.
Describe in a paragraph what happens
when the C2 link is lost. Include UAS actions and flight crew actions.
5.5.2.
Describe how the UAS responds if the
command link is never re-established?
5.5.3.
Recognition of loss - Operator and UAS
5.5.3.1.
Explain how the operator recognizes loss
of the command link?
