Attachment_(L-18)_NAVAIR_Cat_3_Flight_Clr_TO_3_Atth_(1).xls

XLS spreadsheet 252 KB Posted Nov 9, 2016

Attached to: Close Range Unmanned Aircraft Systems (UAS), Intelligence, Surveillance and Reconnaissance (ISR) Services
Solicitation number: N00019-16-R-0063
Issued by: Department of the Navy Naval Air Systems Command

About this file

From the source

Attachment (L-18) Flight Clearance Task Order Attachment (1)

View the file

Other files

File	Type	Posted
Attachment_(L-13)_NAVAIR_Land_Based_OIR_Site_1&2_TO_2_12_Dec_16.pdf	PDF	Dec 12, 2016
Amendment_0001.pdf	PDF	Dec 12, 2016
Attachment_(L-15)_Vol_3_CE-2_ACE.xlsx	XLSX spreadsheet	Nov 9, 2016
Attachment_(L-3)_Vol_1_NVTherm.xls	XLS spreadsheet	Nov 9, 2016
Attachment_(L-12)_NAVAIR_Sea_Based_USN_TO_1.pdf	PDF	Nov 9, 2016
Attachment_(L-9)_Vol_2_Staffing_-_Sea_Based.xls	XLS spreadsheet	Nov 9, 2016
Attachment_(L-14)_Vol_3_CE-1_Contract_Data.xlsx	XLSX spreadsheet	Nov 9, 2016
Attachment_(L-11)_Vol_2_T-2.1 T-2.2.xlsx	XLSX spreadsheet	Nov 9, 2016
Attachment_(L-10)_Vol_2_Staffing_-_Land_Based.xls	XLS spreadsheet	Nov 9, 2016
Attachment_(L-6)_Vol_2_UAS_Maturity.docx	DOCX document	Nov 9, 2016
Attachment_(3)_DD254_signed.pdf	PDF	Nov 9, 2016
Exhibit_(A)_CDRL_Final.doc	DOC document	Nov 9, 2016
Attachment_(L-16)_Vol_4_Price_-_Sea_Based.xls	XLS spreadsheet	Nov 9, 2016
Attachment_(L-4)_Vol_1_Payload_Data.docx	DOCX document	Nov 9, 2016
Attachment_(L-17)_Vol_4_Price_-_Land_Based.xls	XLS spreadsheet	Nov 9, 2016
Attachment_(L-18)_NAVAIR_Cat_3_Flight_Clr_TO_3.pdf	PDF	Nov 9, 2016
Attachment_(L-8)_Vol_2_Propulsion.docx	DOCX document	Nov 9, 2016
Attachment_(L-5)_Vol_2_T-1_CRM.xlsx	XLSX spreadsheet	Nov 9, 2016
Final_Solicitation_9_Nov_FINAL.pdf	PDF	Nov 9, 2016
Attachment_(L-12)_NAVAIR_Sea_Based_USN_TO_1_Atth_(2).xlsx	XLSX spreadsheet	Nov 9, 2016
Attachment_(L-13)_NAVAIR_Land_Based_OIR_Site_1 2_TO_2_Atth_(2).xlsx	XLSX spreadsheet	Nov 9, 2016
Attachment_(L-2)_Vol_1_SSCam_IP_EO.xls	XLS spreadsheet	Nov 9, 2016
Attachment_(L-13)_NAVAIR_Land_Based_OIR_Site_1 2_TO_2.pdf	PDF	Nov 9, 2016
Attachment_(L-7)_Vol_2_AVP_Data.xlsx	XLSX spreadsheet	Nov 9, 2016
Attachment_(L-1)_Vol_1_ES_Tables.xlsx	XLSX spreadsheet	Nov 9, 2016
N00019-16-R-0063_Draft_RFP_Q A_27_Oct_2016.pdf	PDF	Oct 27, 2016
Attachment_(L-15)_Vol_3_CE-2_ACE.xlsx	XLSX spreadsheet	Oct 5, 2016
Attachment_(L-12)_NAVAIR_Sea_Based_USN_TO_1_(peer_review).pdf	PDF	Oct 5, 2016
Attachment_(3)_DD254_signed.pdf	PDF	Oct 5, 2016
Attachment_(L-3)_Vol_1_NVTherm.xls	XLS spreadsheet	Oct 5, 2016
Attachment_(L-10)_Vol_2_Staffing_-_Land_Based.xls	XLS spreadsheet	Oct 5, 2016
Attachment_(L-1)_Vol_1_ES_Tables.xlsx	XLSX spreadsheet	Oct 5, 2016
Attachment_(L-18)_NAVAIR_Cat_3_Flight_Clr_TO_3_Atth_(1).xls	XLS spreadsheet	Oct 5, 2016
Attachment_(L-11)_Vol_2_T-2.1 T-2.2.xlsx	XLSX spreadsheet	Oct 5, 2016
Attachment_(L-2)_Vol_1_SSCam_IP_EO.xls	XLS spreadsheet	Oct 5, 2016
Attachment_(L-9)_Vol_2_Staffing_-_Sea_Based.xls	XLS spreadsheet	Oct 5, 2016
Attachment_(L-12)_NAVAIR_Sea_Based_USN_TO_1_Atth_(2).xlsx	XLSX spreadsheet	Oct 5, 2016
Attachment_(L-14)_Vol_3_CE-1_Contract_Data.xlsx	XLSX spreadsheet	Oct 5, 2016
Attachment_(L-17)_Vol_4_Price_-_Land_Based.xls	XLS spreadsheet	Oct 5, 2016
Draft_Solicitation_N00019-16-R-0063.pdf	PDF	Oct 5, 2016
Attachment_(L-18)_NAVAIR_Cat_3_Flight_Clr_TO_3.pdf	PDF	Oct 5, 2016
Attachment_(L-6)_Vol_2_UAS_Maturity.docx	DOCX document	Oct 5, 2016
Attachment_(L-7)_Vol_2_AVP_Data.xlsx	XLSX spreadsheet	Oct 5, 2016
Attachment_(L-5)_Vol_2_T-1_CRM.xlsx	XLSX spreadsheet	Oct 5, 2016
Attachment_(L-16)_Vol_4_Price_-_Sea_Based.xls	XLS spreadsheet	Oct 5, 2016
Attachment_(L-8)_Vol_2_Propulsion.docx	DOCX document	Oct 5, 2016
Attachment_(L-13)_NAVAIR_Land_Based_OIR_Site_1 2_TO_2.pdf	PDF	Oct 5, 2016
Attachment_(L-4)_Vol_1_Payload_Data.docx	DOCX document	Oct 5, 2016
Attachment_(L-13)_NAVAIR_Land_Based_OIR_Site_1 2_TO_2_Atth_(2).xlsx	XLSX spreadsheet	Oct 5, 2016
Exhibit_(A)_CDRL.pdf	PDF	Oct 5, 2016

Show all 50

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

DISCLAIMER

	DISCLAIMER
1	This spreadsheet is only intended to serve as a reference and does not constitute a binding agreement between the facilitating Class Desk SE, a particular PM discipline, AIR 4.0P, or the person/parties requesting a NAVAIR SOF IFC.
2	This reference is not complete as not all PM disciplines have been represented. Additionally, some of the PM's represented have not formally reviewed this document for accuracy of information. This document was created by the Close Range UAS Class Desk (AIR 4.1.15 - Gary McQuay). It's purpose is to help requestors of UAS SOF IFC's better understand what types of data may be required to support a NAVAIR SOF IFC early-on before the IFC process is started.
3	The data requirements in this document were extracted/derived/compiled from past UAS SOF IFC's that AIR 4.1.1.5 has facilitated. It should be understood that a particular PM could require more or less data than what is listed for his/her particular discipline depending on the nature and circumstances of the IFC request.
4	This reference guide could be updated at any time with new information.

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

IFC Process

	The NAVAIR UAS IFC Process Explained…
1	The requesting organization makes a request for a NAVAIR UAS IFC. This is typically done through the 4.0P Airworthiness office.
2	The Class Desk Systems Engineer and the Airworthiness Office (4.0P) set up a Pre-Planning Meeting (PPM). The PPM serves as a means to allow the IFC requestor(s) and the NAVAIR IFC team to communicate directly with one another about the program in question.
3	At the PPM, the requesting organization briefs the Class Desk, 4.0P, and the engineering performance monitors (PM's) of their program objectives. The Class Desk, 4.0P, and the PM's take the opportunity to communicate to the requesting organization general data requirements that will have to be met before an IFC can be drafted and issued. As a side note, PM's serve as the technical experts who ensure that the IFC is drafted in such a way that risk to personnel/property and/or the system itself is within acceptable limits (as pertains to their particular engineering discipline).
4	If decided that a NAVAIR IFC is required, the Class Desk and 4.0P create a "chop list" of all PM's that must review/approve (i.e., "chop") the IFC.
5	Once the chop list is created, the Class Desk generates an IFC request with the help of the requesting organization and submits the request through the 4.0P website (https://airworthiness.navair.navy.mil/index.cfm?fuseaction=PublicHome.Home). The IFC request will serve as a draft IFC. As such, the IFC request will contain details regarding the system configuration and operating envelope/limits required to meet the program objectives.
6	4.0P then generates a "draft" IFC from the IFC request and utilizes their web-site to notify all PM's of their new IFC work assignment.
7	The requesting organization then provides the appropriate amount of funding to the IFC team (Class Desk, Flight Test, PM's) and immediately begins providing the PM's with data to answer their preliminary data requirements. This will often be an iterative and somewhat rigorous process wherein answers to PMs' questions will often generate additional data requirements. A NAVAIR IFC cannot be issued without funding!
8	As data is exchanged between the requesting organization and the engineering PM's, the PM's will individually modifiy the IFC draft as appropriate until they are satisfied that, with respect to their particular discipline, the system poses minimal risk to personnel and property (Safety of Flight IFC) or additionally, if required, that it can safely attain, maintain, and terminate flight (Airworthiness IFC). The Class Desk and 4.0P will facilitate the data exchange process.
9	If it happens that data requested by the PM's does not exist, then the following options can be taken to generate the requested data: (1) analysis/simulation, (2) lab/ground testing, and/or (3) flight testing. If, for some reason, it is still not possible to generate data that the Class Desk, 4.0P, and the PM's feel is necessary for IFC issuance, then the following options exist: (1) the IFC envelope/limits and/or configuration will have to be restricted/modified to bring risk to an acceptable level, and/or (2) appropriate "Warning", "Caution", and "Notes" statements will have to be added to the IFC that warn operators of identified risks and instruct them how to effectively mitigate them, and/or (3) the appropriate authority level will have to approve the risk level in the absence of a risk mitigation plan, or (4) NAVAIR will not issue an IFC.
10	Once all PM's have signed off on the IFC, the Class Desk reviews and gives his/her final approval/signature.
11	The 4.0P Senior UAS Engineer must then provide his/her final approval/signature.
12	4.0P then generates and distributes a final IFC to all appropriate organizations/personnel.

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.1.1.5 - Systems Eng

	AIR CODE:		4.1.1.5
	ENGINEERING DISCIPLINE:		Systems Engineering (PMA-263 Close Range UAS Class Desk)
			NAME		WORK PHONE		WORK EMAIL
	Class Desk Engineer(S):
	DATA REQUIREMENTS:
1	UAS Type/Series/Model:
2	Original Equipment Manufacturer (OEM):
3	Program Funding Sponsor(s) (ONR, NRL, Congress, NAVAIR SBIR, etc..):
4	All Essential Technical POC's (OEM, Contracting Agency, etc. - name, phone, email info):
	Name			Phone				Email
	1
	2
	3
	4
5	All Essential Program Management POC's (name, phone, email info):
	Name			Phone				Email
	1
	2
	3
	4
6	Max GTOW:	Wingspan:		Length:		MAX Speed:		Endurance:
7	Take-off Method(s):
8	Landing/Recovery Method(s):
9	Payload Capability:
10	Method of Propulsion:
11	Intended CONOP's of UAS system:
12	Who owns the assets that will be flown (USN, USMC, USA, Contractor, ONR, etc.):
13	Does the owner consider the system to be expendable and probability of loss acceptable?
14	Who will be operating the assets (USN, USMC, USA, Contractor, etc.):
15	What type of airspace will assets be operated in?
	a. Restricted Airspace(s):
	b. National Airspace(s):
16	What types of operations will the SOF IFC support (performance testing, operational testing, proof-of-concept testing, CONOP's development, deployment to end users, etc.):
	Is over-flight of any personnel required during flight ops?
17	What is the requestor's IFC need date:
18	How long with the IFC need to be valid for:
19	Past experience with configuration to be performed (total flight hours, number of in-flight failures, reliability data such as MTBR, MTBF, etc.):
20	Does a Pilot Training Program exist? Have/will intended operators taken/take this program prior to operations?
21	Does a Maintenance Program exist? Can an Operation/Maintenance Manual be provided for review?
22	Does a Configuration Management Program exist?

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.4 - Propulsion

	AIR CODE:	4.4.1
	ENGINEERING DISCIPLINE:	Propulsion
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Description of entire propulsion system (fuel system, lubrication system, ignition system, propeller, alternator, etc.)
2	If more than one configuration, provide details of how they differ
3	Engine performance characteristics
4	Engine test and/or operational history
5	Engine reliability data (total flight hrs per configuration, mean time between failures, etc.)
6	Maintenance/operating manuals
7	Maintenance intervals (for all critical components: engine, spark plugs, magnetos, air filters, etc.)

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.4.4 - Electrical Power

	AIR CODE:	4.4.4.1
	ENGINEERING DISCIPLINE:	Electrical Power
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Electrical load analysis/survey (power budget) for all on-board avionics, payloads, etc.
2	Specifications for all batteries and engine alternator
3	Wiring diagrams and schematics

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.4.5 - Wiring

	AIR CODE:	4.4.4.3
	ENGINEERING DISCIPLINE:	Wiring
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1
2
3

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.4.5 - Fuels & Lubes

	AIR CODE:	4.4.5
	ENGINEERING DISCIPLINE:	Fuels and Lubricants
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Fuel type and spec
2	Lube types and spec and how used
3	Fuel system and lubrication system description (similar to above)

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.9.7 - Materials

	AIR CODE:	4.9.7
	ENGINEERING DISCIPLINE:	Materials
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Materials used on the system (and were they purchased to a specification?)
2	Protective finish scheme employed
3	Dissimilar material contact areas
4	Hazardous materials used
5	Inspection procedures followed
6	For water landings, procedures for readying the UAV for the next flight (is system cleaned, rinsed, inspected for corrosion, etc.)
7	Materials manufacturing scheme(s)

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.3.2.6 - Flight Controls

	AIR CODE:	4.3.2.6
	ENGINEERING DISCIPLINE:	Flight Controls
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Air vehicle system description
2	Flight Control System (FCS) design description
	a. Functional block diagram
	b. FCS performance summary/description
	c. FCS components layout and analysis
3	Risk assessment and mitigation
4	Lessons-learned including all FCS related trouble reports
5	FCS component drawings and specifications
6	Aircraft envelope and limitations
7	Flight Controls Software Design
	a. Block Diagrams of Inner and Outer Loops of Controller
	b. Description of Controller Design Process to ensure controller stability
	c. Description of any Aerodynamic, Sensor, Actuator, and Gear Models used in design
	d. S/W configuration control and management
	e. Regression analysis and testing procedures
8	FTS system design as it interfaces with Flight Controls
9	Flight test instrumentation description

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.3.2.4 - Flying Qualities

DATA REQUEST FOR	POCs:
4.3.2.4 FLIGHT DYNAMICS
Purpose: To list the data requested to secure a recommended airworthiness flight clearance for UAVs. This list is intended as a starting point to communicate data requests. Specific requests may be tailored based upon the purpose of the requested flight clearance. This is not intended to be the final data requirements list, but captures major areas to define the UAV flight dynamics.
	Data Available?
1. Basic Questions:	YES	NO	N/A	Remarks
a. What is the name of the UAV?
b. What types of flight clearances are requested?				Test FC____Restricted Airspace FC_(SOF) Deployment____
c. How many configurations of the vehicle will be operational?
d. What configurations are applicable for the flight clearance?
e. How many flight hours planned on each configuration?
f. What is the flight test development program plan?
g. How many incidents/accidents have occurred?
1. What have been the causal factors of the incidents/accidents?
h. What is the desired flight envelope: Altitude range, Airspeed range, Crosswinds, GW range, CG range.
i. What is the desired wind envelope and shipboard launch/recovery envelope?
j. Mass properties data?
k. What are the methods used to record quantitative data? (autopilot, GCS recorder, etc.)
l. What are the parameters that are available as recorded quantitative data?
m. What is the recording rate for quantitative data?
n. How many software configurations will be authorized?
o. Are software gains adjustable by the user?
p. What autonomous modes are available?
q. Total flight hours on this UAV?
r. How many vehicles are in flight status?
	Data Available?
2. Design Data:	YES	NO	N/A	Remarks (or Documents identified)
a. What aircraft design/configuration data exists (detailed three-view drawings with dimensions, 2-D airfoil data, wing area, designed stability parameters, etc.)				Must haves: Moments of Inertia [Ixx, Iyy, Izz, Ixz]

- X, Z Location of Aero Moment Center

- Airfoil(s) (wing & tail)

- X,Y, & Z CG location

- Cruise Altitude

b. What empirical aerodynamic data exists (e.g., CFD, panel code, wind tunnel, flight PID data)?
1. How many configurations (e.g. landing, take-off, conversion, cruise)?
2. Ground effects data?
c. What propulsion data exists?
d. What performance/S+C analyses have been performed?
1. Stall speed?
2. Max ceiling?
3. Endurance?
4. Basic static stability?
5. Dynamic stability (short period, phugoid, Dutch roll)?
6. Basic time constants (roll mode, spiral mode, etc.)?
7. Attitude quickness?
8. Frequency response?
e. What controls information/analyses exists?
1. Phase/gain margins?
2. Air data calibrations?
3. FMEAs?
4. Control System Description?
5. Control law diagrams?
f. Is there a simulation?
1. What models exist?
2. What is the process for model validation?
3. Flight Test Data (Manual and Autonomous Modes, as required):
3.1 Quantitative				Remarks (or Documents identified)
				please be more specific regarding following test requirements
a. Static Longitudinal Stability
b. Dynamic Long Stab
1. Short Term (e.g., pitch doublets)
2. Long Term
c. Static Lateral-Directional Stability
1. Steady Heading Sideslips
2. Turns on One Control
3. Bank-to-bank rolls
d. Dynamic Lat-Dir
1. Release from SHSS
2. Roll doublets
3. Yaw doublets
e. Maneuvering Stability
f. Control Response (all axes)
g. Trimmed Flight Control Positions (TFCPs) in Level Flight
h. TFCPs in Climbs/Descents
i. Stall Characteristics
j. Low Speed Flying Qualities
1. Critical Azimuth (rotary wing aircraft)
2. Approach Characteristics
k. Launch/Recovery Characteristics
1. Manual
2. Autonomous
3. Degraded modes (i.e., flight control system failure characteristics)
l. Autonomous characteristics
1. Waypoint capture accuracy
2. Ride qualities in autopilot
	Data Available?
3.2 Qualitative	YES	NO	N/A	Remarks
a. Pitch Attitude Captures (Quantitative/Qualitative)
b. Roll Attitude Captures (Quantitative/Qualitative)
c. Trimmability
d. Pilot feedback
NOTES

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.3.2.5 - Performance

	AIR CODE:		4.3.2.2
	ENGINEERING DISCIPLINE:		Aero Performance
			NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Existing Flight Clearance
	a. Configuration Description
	b. Performance
		Flight Envelope
		Mission Performance
	c. Limitations
		Wt & CG envelope
2	Requesting Flight Clearance
	a. Configuration Description
		OML Changes
		Propulsion Changes
		Payload power and cooling requirements
		Effects on Air Data System
	b. Weight & CG
	c. Performance
		Flight Envelope
		Operating Procedures changes
		Mission Performance
3	Launch Envelope:
	a. Max Head Winds
	b. Max Cross Winds
	c. Pre-launch Check to determine if satisfactory engine motor performance for launch.
	d. Hazard area
	e. Max Climb rate to determine launch climb out clearance requirements
	f. Stall speed
	g. Launcher performance (end speed)
	h. Max Density Altitude
4	Recovery:
	a. Recovery area definition (hazard area)
	c. Wave-off Performance
	d. Night recovery
	e. Stall speed
	f. Approach Profile (airspeed)
	g. Max Headwinds
	h. Max Cross winds
	i. Max Density Altitude
5	Up&Away Performance:
	a. Flight Envelope
	b. Max Speed
	c. Stall Speed
	d. Ceilings
	e. Cruise & Loiter Performance
		Fuel Flow
		Airspeed
		Engine Power
	f. Rate of Climb
	g. Max Bank Angle
6	Additional:
	a. Basic Aerodynamic Data Report
	b. Substantiating Performance Report
	c. Flight manual (NATOPS equivalent)
	d. Test plan (if one exists)

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.3.3 - Strength & Loads

	AIR CODE:	4.3.3
	ENGINEERING DISCIPLINE:	Strength, Flight Loads, Landing Loads, & Dynamic Loads
		NAME	AREA	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Assist the AIR 4.3.3.3 team in arriving at realistic Flight, Landing, and Dynamic Load Factors for the UAS in question.
2	Work with AIR 4.3.3, Class Desk SE, and AIR 4.0P to determine what types of analyses and/or testing will be required to satisfy constraints of the requested IFC.
3	Maximum Data Requirements for STRUCTURAL ANALYSIS:
	a. Provide a standalone Stress and Loads Analysis report containing calculations and conclusions.
	b. The structural analysis shall clearly show all calculations, references, critical structure Margins of Safety (MS), free-body diagrams, assumptions, and methodologies.
	c. Any preparatory reference must be submitted as part of the analysis for review.
	d. No Plastic Bending analysis shall be used.
	e. Stresses used shall be Principal (Ultimate Load) not Von Mises (Limit Load).
	f. Load cases to be used for the structural analysis are defined by AIR-4.3.3.3.
	g. Material Strengths to be Taken From MIL-HDBK-5 / MMPDS, Column “A” Values where available.
	h. Static Elastic Analyses with Positive Structural Margins:
	i. 0.15 Additional Margin for Lugs and Fittings
	ii. 0.33 Additional Margin for Castings
	iii. 2.00 Additional Margin for Bearing Factor
	iv. Applicable Margin For Fiber Reinforced Composite Structure (wet/dry Strength Allowable)
	v. Applicable Summation of Margins do Apply
	i. For Metal, Composite, and Wood Structure, Flight and Ground Load Margins to Account for 1.5 x Limit Loads (Ultimate)
	j. No Yielding allowed at 1.15 x Limit Load
	k. Crash Loads (ground) are Considered Ultimate
4	Maximum Data Requirements for STATIC AIRFRAME TESTING:
	a. All critical areas must be addressed by analysis and/or static testing. If a Loads and Strength analysis is not an option, static testing to 1.15 x limit (no yielding allowed) and ultimate (1.50 x limit with no failure allowed) loading will be required.
	b. The following critical areas must be included (if applicable): landing gear, wing panels (wing root, spar), empennage/tail boom, tail boom-to-fuselage attachment, engine-to-fuselage attachment, and catapult/arresting aircraft structure. Include all other Safety of Flight critical areas or of structural interest in the report.
	c. If amphibian, wet/dry conditions must be taken into account. Option 1, add applicable margin (factor) for fiber reinforced composite structure to flight and ground loads. Option 2, test under wet conditions. Representative coupon testing may be used.
	d. All loads used for testing must have AIR-4.3.3.3 (Loads & Dynamics) concurrence. Structural test plan must have AIR-4.3.3.2 concurrence.
	e. Static testing, procedures, findings, and conclusion will be documented in a report.
	f. Report will be stand-alone with details allowing test to be recreated.
5	Preferred Airframe STRUCTURAL DESIGN REQUIREMENTS:
	a. Welding is not preferred. Contact AIR-4.3.3.2 for specific applications.
	b. Castings are not preferred. Contact AIR-4.3.3.2 for specific applications.
	c. Hardware (fasteners, nut plates, nuts, Hi-Loc, collars, rivets, etc.) strengths to be taken from specific hardware specification.
	d. NA 01-1A-8, Structural Hardware Manual strengths can be used if strengths are not provided in specific specification.
	e. NA 01-1A-1, General Manual for Structural Repair can be used as guidance for structural design and repairs.
	f. MIL-HDBK-5 / MMPDS hardware strengths can be used if strengths are not provided in specific specification.
	g. Fasteners (bolts, screws) that are below 125 KSI Ftu or above 220 KSI Ftu are not to be used.
	h. Rivets tension loads shall not exceed 10% of the specified rivet shear strength and shall not be the primary applied load.
	i. Fastening systems with known and proven positive locking mechanisms are to be used.
6	Preferred STRUCTURAL FEA REQUIREMENTS (if FEA is used):
	a. Loads (Px, Py, Pz, Mx, My, Mz) to be taken from model for use with classic analyses techniques.
	b. Include Free Body Diagram.
	c. Validity of Model; Verify, document, and report verification that the sum of the respective boundary reaction loads and moments “zero out”.
	d. Validity of Model; Verify, document, and report comparison of model results to known and accepted closed form solution methods. The two should equal.
	e. Provide written description of model. (number of elements and types, how elements were used, number of nodes, did the model run, error value, FO 6 file data for NASTRAN).
	f. Provide node schematic showing numbered node locations.
	g. Provide node results table relating back to schematic.
7	Preferred IFC Date Package Requirments:
	a. Stress, loads, and/or static test report(s) showing the installation and/or modification to be structurally adequate for flight.
	b. Drawing package. Submitted with the structural report as a reference. Drawings must show details, sub assemblies, and installation. Drawings to provide enough information for fabrication, assembly, procurement, installation, and quality control.
	c. Any and all references used in the report that are not common; i.e., preparatory information.
	d. Reporting in an Electronic Format is Preferred.
8	Loads Checklist:
	a. Mass properties - weight, Center of Gravity (CG), Ixx, Iyy, Izz.
	b. Flight loads analysis - include load trends and design load cases.
	c. Ground loads analysis - include load trends and design load cases.
	d. Strength Summary and Operating Restrictions report.
	e. Structural Design Criteria Report - includes maneuver weights, load factors, design speeds.

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.9.3 - Weight & Bal

	AIR CODE:	4.9.3
	ENGINEERING DISCIPLINE:	Weight And Balance
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	C.G. envelope data and how it was arrived at
2	Vehicle weight information and distribution data (for all possible payload configs)

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.6 - Human Systems

	AIR CODE:	4.6
	ENGINEERING DISCIPLINE:	Human Systems
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Operating Manual
2	Description of Launch/Recovery Procedures
3	Description of flight modes
4	Emergency Procedures
5	A description of the functional and physical flows of the ground station data/information (this includes flight information displays, control mode annunciation, failure detection and annunciation, and control logic)
6	Handling procedures
7	Interface documents
8	Need to know if NVGs will be used during operation
9	Anything that relates to the position of the operators

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.1.10.2 - SW Safety

	AIR CODE:	4.1.6.2
	ENGINEERING DISCIPLINE:	Software Safety
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	MAXIMUM DATA REQUIREMENTS:
1	Compliance with a Systems Safety Program Plan that includes software safety issues, or a stand-alone Software Safety Program Plan
2	Having a System Safety Working Group within which the members assess and collect evidence/documentation that no system components (harware, software, or human system integration) can contribute to the loss of life, property, or environment. The System Safety Working Group is to be chaired by Government and Contractor System Safety Leads.
3	Having performed an initial severity assessment of system functionality via the NAVAIR Hazard Risk Index (HRI)
4	Having executed a Hazard Analysis (PHL & PHA) for functional hazards:
	PHL – Development of a Preliminary (System) Hazards List that can be contributed to by any system-level component (hardware, software, or human system integration)
	PHA – Development of a categorized and prioritized Preliminary Hazards List (functional) specific to the system, that can be contributed to by the hardware, human, or the software (including software environment in which the system is built)
7	Identification of all the (functional) casual factors for each prioritized hazard
8	Identification of the derived (functional) mitigating safety-critical requirements for each causal factor
9	Having updated the severity assessment using the HRI approach
10	Having tailored the Generic (i.e. Common Global) Software Safety-Critical Requirements Lists, usually in an appendix, as they apply to the system
11	Identification of the mitigating Generic (i.e. Common Global safety-critical requirements
	a. Having executed Hazard Analysis (SSHA and SHA) for functional hazards
	1a. Refinement of the SSHA analysis by linking the causal factors to their mitigating requirements (especially with respect to COTS/GOTS interfacing)
	2a. Refinement of the SHA analysis by performing an interface hazard analysis between subsystems within the system with regard to hardware, software, and human systems integration causal factors
12	Having executed Process analysis/testing by tracing the Generic (i.e. Common Global) Software Execute Product analysis/testing by tracing the functional Software Safety-Critical Requirements to test
13	Having executed “Safety” Tests on Software Safety-Critical Requirements at the appropriate level of rigor (ex. Level I, II, or III Software as identified in the NAVAIR Flight Clearance Instruction)
14	Having identified mitigating evidence and any residual risk for inclusion within the overarching System Safety Assessment Report (SAR).
15	Having executed regression analysis/testing of the system when there is a change. (i.e., a mod to the baseline, or a mod for a particular flight test)
16	An audit trail for all of the above items, and substantiating data for safety decisions

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.1.6 - System Safety

	AIR CODE:	4.1.7
	ENGINEERING DISCIPLINE:	System Safety
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
1	Overall system description
2	How UAV will be used
3	Where UAV will be used (i.e, what type of environment)
4	Operator’s manual(s)
5	Types of hazardous materials employed (batteries, fuels, etc.)
6	Hazard and/or flight contingency analysis (if ones exist)
7	Reports of all previous incidents/mishaps
8	Range safety analysis report (if one exists)

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

4.1.7 - E3

	AIR CODE:	4.1.7
	ENGINEERING DISCIPLINE:	Electromagnetic Environmental Effects (E3)
		NAME	WORK PHONE	WORK EMAIL
	PERFORMANCE MONITOR(S):
	DATA REQUIREMENTS:
	The following would provide electromagnetic environmental effects (E3) support for a proposed flight clearance. Most flight clearances will require only an applicable subset of this data. See the latest version of MIL-STD-464 for details of aircraft- and system-level E3 requirements.
1	Describe the system or modification for which the flight clearance has been requested. Do not neglect ancillary equipment, if this equipment is used when aircraft engines are on. (An obvious example of such ancillary equipment would be a land- or ship-based “command and control” console for unmanned aerial vehicles.)
	a. Include an overall description of constituent electronic/electrical components and wiring, whether new, modified, or deleted.
	b. Include the frequencies, powers, modulations and bandwidths of any radio-frequency (RF) transmitters or receivers. Also include antenna types and gains. Cite any submittals of DD Form 1494, “Application for Equipment Frequency Allocation”.
	c. Include changes to software which might affect the action of a component in response to electrical noise or disruption.
	d. Include changes to mechanical components---those which might adversely affect lightning safety, accumulation of electrostatic charge, or other E3-related concerns.
	e. Include additions, deletions, or changes with respect to electrically-initiated explosive devices (including munitions).
2	Describe any manner in which the requested flight clearance involves---or might affect---flight-critical equipment. (Flight-critical equipment is usually listed in the NATOPS---for military systems---or in an operating/servicing manual). Describe the manner is which flight safety might be degraded by disruption or malfunction of the system/modification described in the requested flight clearance.
3	Describe the intended operational environments.
	a. Describe where the system will be used (For example, will flight be limited to restricted airspace above sparsely-populated military ranges, or could flight occur anywhere in the world? Will the system be used aboard one or more classes of air-capable Navy ships?)
	b. State whether or not operations might be conducted when lightning is a possibility.
4	Describe the measures taken to ensure proper E3 performance of the system or modification covered by the requested flight clearance.
	a. Summarize specific design steps taken to ensure adequate E3 performance, such as those relating to electrical cable design, electrical/electronic circuit design, electrical shielding, continuity of electrical shielding, electrical bonding of mating surfaces, etc.
	b. Summarize steps taken to preclude radiation hazards: hazards of electromagnetic radiation to personnel (HERP), to ordnance (HERO), and to fuel (HERF). Summarize the details and results of any tests (or analyses), and describe any necessary precautions (such as “keep away” distances).
	c. Summarize the details and results of electromagnetic interference (EMI) tests of constituent equipment. (Ideally, tests would be in accordance with the latest version of MIL-STD-461.)
	d. Describe the operating modes and results of electromagnetic compatibility (EMC) tests, including any EMC safety-of-flight tests (SOFTs).
	e. Summarize the details and results of immunity testing (or analyses) against disruption by external RF emitters.
	f. Summarize the details and results of susceptibility tests against electrostatic discharge (ESD), such as ESD caused by handling of electronic equipment, ordnance, or the constituents of either.
	g. Summarize the details and results of testing against the adverse effects of precipitation static on RF receivers.
	h. Describe the testing and measures taken to assure that neither direct nor indirect effects of lightning will impair flight safety.
	I. Summarize the details and results of testing to assure that spurious RF emissions will not reveal aircraft presence to hostile forces. (MIL-STD-464 refers to this as emissions control, or EMCON.)
5	If the system processes classified information, cite the required TEMPEST test or TEMPEST vulnerability assessment.

&R&"Arial,Bold"N00019-16-R-0063 Attachment (1) to Task Order Three PMA 263 UAS Flight Clearance Data Requirements List Page &P of &N &A

File details come from the government source that posted it. Updated Nov 14, 2017.