1、Designation: F3196 17Standard Practice forSeeking Approval for Extended Visual Line of Sight (EVLOS)or Beyond Visual Line of Sight (BVLOS) Small UnmannedAircraft System (sUAS) Operations1This standard is issued under the fixed designation F3196; the number immediately following the designation indic
2、ates the year oforiginal adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.1. Scope1.1 Compliance with this practice is recommende
3、d as onemeans of seeking approval from a civil aviation authority(CAA) to operate a small unmanned aircraft system (sUAS) tofly extended visual line of sight (EVLOS) or beyond visual lineof sight (BVLOS), or both. Any regulatory application of thispractice to sUAS and other unmanned aircraft systems
4、 (UASs)is at the discretion of the appropriate CAA.1.2 UnitsThe values stated in inch-pound units are to beregarded as the standard. The values given in parentheses aremathematical conversions to SI units that are provided forinformation only and are not considered standard.1.3 This standard does no
5、t purport to address all of thesafety concerns, if any, associated with its use. It is theresponsibility of the user of this standard to establish appro-priate safety and health practices and determine the applica-bility of regulatory limitations prior to use.2. Referenced Documents2.1 ASTM Standard
6、s:2NOTE 1For requirements in these standards that are specified to beadequate, the applicant/proponent shall propose and obtain approval of thespecifics of that requirement from the CAA.F2908 Specification for Aircraft Flight Manual (AFM) for aSmall Unmanned Aircraft System (sUAS)F2909 Practice for
7、Maintenance and Continued Airworthi-ness of Small Unmanned Aircraft Systems (sUAS)F2911 Practice for Production Acceptance of Small Un-manned Aircraft System (sUAS)F3002 Specification for Design of the Command and Con-trol System for Small UnmannedAircraft Systems (sUAS)F3003 Specification for Quali
8、ty Assurance of a Small Un-manned Aircraft System (sUAS)F3005 Specification for Batteries for Use in Small Un-manned Aircraft Systems (sUAS)F3178 Practice for Operational Risk Assessment of SmallUnmanned Aircraft Systems (sUAS)F3201 Practice for Ensuring Dependability of SoftwareUsed in Unmanned Air
9、craft Systems (UAS)3. Terminology3.1 Definitions of Terms Specific to This Standard:3.1.1 applicant/proponent, nthe person or organizationresponsible for seeking the approval to operate or the person ororganization operating an sUAS, or both. The applicant/proponent may be one of the following entit
10、ies:3.1.1.1 manufacturer, nthe person or organization whocauses production of a product or article. A manufacturer mayalso be an operator.3.1.1.2 operator, nthe person or organization that appliesfor CAAapproval to operate an sUAS or who seeks operationalapproval for types of flight operations prohi
11、bited by a CAA forthat sUAS.3.1.1.3 original equipment manufacturer, OEM, nthe per-son or organization who first produced that particular productor article. An OEM may also be an operator.3.1.2 beyond visual line of sight, BVLOSoperation whenthe individual(s) (for example, pilot or VO) responsible f
12、orcontrolling the flight of the sUAcannot maintain direct unaided(other than with the use of spectacles/contacts lenses orsunglasses, or both) visual contact with the sUA other aircraft,terrain, or obstacles to determine whether the sUA endangerslife or property or both.3.1.2.1 DiscussionTechnologic
13、al means may be used fordetermining the sUAs movement relative to intruding aircraft,obstacles, and terrain; observe the airspace for other air trafficor hazards; and determine whether the sUA endangers life orproperty or both.3.1.3 command and control (C2) link(s), nradio-frequencylink(s) between t
14、he control station and the unmanned aircraft1This practice is under the jurisdiction of ASTM Committee F38 on UnmannedAircraft Systems and is the direct responsibility of Subcommittee F38.01 onAirworthiness.Current edition approved Feb. 15, 2017. Published March 2017. DOI: 10.1520/F3196-17.2For refe
15、renced ASTM standards, visit the ASTM website, www.astm.org, orcontact ASTM Customer Service at serviceastm.org. For Annual Book of ASTMStandards volume information, refer to the standards Document Summary page onthe ASTM website.Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West
16、 Conshohocken, PA 19428-2959. United StatesThis international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for theDevelopment of International Standards, Guides and Recommendations issued by the World Tra
17、de Organization Technical Barriers to Trade (TBT) Committee.1(UA), also known as the control and non-payload communi-cations (CNPC) link(s).3.1.4 control station, ninterface used by the Remote Pilotin Command (RPIC) or pilot to control the flight path of thesUA.3.1.5 crew member, nperson charged wit
18、h duties essentialto the operation of an sUAS during a flight duty period.3.1.6 extended visual line of sight, EVLOSoperation whenthe sUA cannot be seen by the individuals responsible forsee-and-avoid with unaided (other than spectacles/contactslenses or sunglasses, or both) vision but where the loc
19、ation ofthe sUA is known through technological means.3.1.6.1 DiscussionEither the RPIC or, alternatively, theVO: can use said technological means for determining thelocation of the sUA to determine its movement relative tointruding aircraft, obstacles, or terrain; observe the airspace forother air t
20、raffic or hazards; and determine whether the sUAendangers life or property or both. To further clarify, technol-ogy means can be used to determine the position of the sUASbut the RPIC or the VO must be able to see the area the sUASis known to be in so as to execute the required see-and-avoidfunction
21、.3.1.7 fly-away, nflight outside of operational boundaries(altitude/airspeed/lateral limits) as the result of a failure,interruption, or degradation of the control element or onboardsystems, or both.3.1.8 fly-away protection system, nsystem that will safelyrecover the sUA, or keep the sUA within the
22、 intendedoperational area, in the event of a fly-away as defined in 3.1.7.3.1.9 licensed band, nany frequency or range of frequen-cies in which transmission requires permission from a govern-ing body (for example, the U.S. Federal CommunicationsCommission).3.1.10 lost link, noccurrence in which the
23、control stationhas lost the ability to maintain positive control of the sUAbecause of the degradation, loss, or interruption of the C2 linkfor longer than deemed safe depending on the circumstances.3.1.11 pilot, nthe RPIC or person other than the RPICwho is controlling the flight of an sUAunder the
24、supervision ofthe RPIC.3.1.12 positive control, ncondition in which commandedchanges in the sUA flight path result in expected and sufficientmaneuver(s) within an expected period of time.3.1.13 remote pilot in command, RPIC, nperson who isdirectly responsible for and is the final authority as to the
25、operation of the sUAS; has been designated as remote pilot incommand before or during the flight of an sUAS; and holds theappropriate CAA certificate for the conduct of the flight.3.1.14 see-and-avoid, vuse of the visual capability of aperson to identify intruding aircraft so that the sUA can bemane
26、uvered and the safe conduct of the flight can be main-tained.3.1.15 sense-and-avoid, vuse of a sensor system to iden-tify intruding aircraft so that the sUA can be maneuvered andthe safe conduct of the flight can be maintained.3.1.16 shall versus should versus may, vuse of the word“shall” means that
27、 a procedure or statement is mandatory andmust be followed to comply with this practice, “should” meansrecommended, and “may” means optional at the discretion ofthe applicant/proponent.3.1.16.1 Discussion“Shall” statements are requirementsand they include sufficient detail needed to define complianc
28、e(for example, threshold values, test methods, oversight, andreference to other standards). “Should” statements are providedas guidance towards the overall goal of improving safety andcould include only subjective statements. “Should” statementsalso represent parameters that could be used in safety
29、evalua-tions or could lead to development of future requirements, orboth. “May” statements are provided to clarify acceptability ofa specific item or practice and offer options for satisfyingrequirements.3.1.17 small unmanned aircraft, sUA, nunmanned aircraftweighing less than 55 lb (25 kg) on takeo
30、ff, including every-thing that is on board or otherwise attached to the aircraft.3.1.18 small unmanned aircraft system, sUAS, nsmallunmanned aircraft and its associated elements (includingcommunication links and the components that control the sUA)that are required for the safe and efficient operati
31、on of the sUAin a national airspace system.3.1.19 unmanned aircraft, UA, naircraft operated withoutthe possibility of direct human intervention from within or onthe aircraft.3.1.20 visual line of sight, VLOS, nwith vision that isunaided other than by corrective lenses or sunglasses, or both,the pilo
32、t or visual observer shall be able to see the sUAthroughout the entire flight to determine its movement relativeto intruding aircraft, obstacles, terrain; observe the airspace forother air traffic or hazards; and determine whether the sUAendangers life or property or both.3.1.21 visual observer, VO,
33、 nperson who is designated bythe RPIC to assist the RPIC or the pilot, or both, to see thesUAS throughout the entire flight to determine its movementrelative to intruding aircraft, obstacles, terrain; observe theairspace for other air traffic or hazards; and determine whetherthe sUA endangers life o
34、r property or both.3.2 Acronyms:3.2.1 AFMaicraft flight manual.3.2.2 BVLOSbeyond visual line of sight.3.2.3 CAAcivil aviation authority.3.2.4 C2command and control.3.2.5 CNPCcontrol and non-payload communications.3.2.6 CONOPSconcept of operations.3.2.7 EVLOSextended visual line of sight.3.2.8 OEMori
35、ginal aircraft manufacturer.3.2.9 ORAoperational risk assessment.3.2.10 RPICremote pilot in command.3.2.11 SDOstandards development organization.3.2.12 sUASsmall unmanned aircraft system.3.2.13 sUAsmall unmanned aircraft.F3196 1723.2.14 UAunmanned aircraft.3.2.15 UASunmanned aircraft system.3.2.16 V
36、LOSvisual line of sight.3.2.17 VOvisual observer.4. Significance and Use4.1 This practice is written for all sUAS seeking permissionto operate EVLOS or BVLOS, or both, in airspace authorizedby a CAA.4.2 It is assumed that the maximum weight, altitude, andairspeed of an sUAS will be specified by a CA
37、A. However,unless otherwise specified by a nations CAA, this practiceapplies to sUA that:4.2.1 Have a maximum takeoff gross weight of less than 55lb (25 kg), including everything that is on board or otherwiseattached to the aircraft, and4.2.2 Are remotely piloted (that is, flown without thepossibili
38、ty of direct human intervention from within or on theaircraft).5. Procedure5.1 The following steps are recommended to seek opera-tional approval to fly an sUAS at EVLOS or BVLOS, or both.Details of each step are provided in the following paragraphs:5.1.1 If required by the CAA, the applicant/propone
39、nt shalldefine the sUA system. See Section 6 for minimum require-ments.5.1.2 The applicant/proponent shall define the CONOPS.See Section 7 for minimum requirements.5.1.3 The applicant/proponent shall perform an ORAfor thetotal system and a proposed CONOPS which identifies pro-posed mitigation strate
40、gies including technology, designcharacteristics, training, operational requirements/limitationsor procedures, or combinations thereof, for the identifiedhazards. See Sections 7 and 8 for minimum requirements.5.1.4 If required to do so by the CAA, the applicant/proponent shall present results of 5.1
41、.1 5.1.3 to the CAA andthen refine them until it is jointly determined that risksassociated with system design and the proposed operation areacceptable.5.1.5 If required to do so by the CAA, the applicant/proponent shall work with the CAA or CAA-approved testorganizations, or both, to verify that th
42、e final system andmitigation strategies meet the agreed-to requirements.5.1.6 The operator shall obtain approval to operate from theCAA.6. System Requirements6.1 If required to do so by the CAA, the operational andairworthiness design requirements in the current versions of thefollowing standards sh
43、all, at a minimum, be complied with byany sUAS flown EVLOS or BVLOS, or both. These require-ments are necessary but may not be sufficient for all EVLOS orBVLOS operations, or both. Depending on the system andCONOPS proposed by the applicant/proponent, additional riskmitigations for the sUAS (see Sec
44、tion 8) may be required toensure an acceptable level of risk.F2908 Specification for Aircraft Flight Manual (AFM) for a Small Un-manned Aircraft System (sUAS)F2909 Practice for Maintenance and Continued Airworthiness of SmallUnmanned Aircraft Systems (sUAS)F2911 Practice for Production Acceptance of
45、 a Small Unmanned AircraftSystem (sUAS)F3002 Specification for Design of the Command and Control System forSmall Unmanned Aircraft System (sUAS)F3003 Specification for Quality Assurance of a Small Unmanned AircraftSystem (sUAS)F3005 Specification for Batteries for Use in Small Unmanned AircraftSyste
46、msF3201 Practice for Ensuring Dependability of Software Used in an sUASStandard for training of pilots and visual observers of sUASpublished by a SDO. See Related Materials sectionfor ASTM Work Item on this topic.Standard for sUAS operations over people published by a SDOOnly required if EVLOS or BV
47、LOS operations or both areproposed to be flown over people. See Related Materialssection for ASTM Work Item on this topic.Standard for design, construction, and verification of a fixed wingsUAS published by a SDO. See Related Materials sectionfor ASTM Work Item on this topic.Standard for design, con
48、struction, and verification of a verticaltakeoff and landing sUAS published by a SDO. See RelatedMaterials section for ASTM Work Item on this topic.7. Operational Risk Assessment (ORA) and Concept ofOperation (CONOPS)7.1 An ORA and CONOPS shall be completed by theapplicant/proponent in accordance wi
49、th Practice F3178 forOperational Risk Assessment (ORA) for an sUAS.7.2 In addition to any hazards identified in the abovepublished ORA standard for an sUAS, hazards specific toeither EVLOS or BVLOS operations shall also be included inthe ORA.8. Risk Mitigation Strategies8.1 Since it is anticipated that each system and CONOPSwill vary considerably, specific risk mitigation strategies anddetails shall be proposed by the applicant/proponent to theCAA for the hazards identified in the ORA. Examples ofvarious types of potential risk mitiga
