1.1 本规程的重点是准备操作风险评估（ORA），用于支持小型无人机系统（SUA）（55磅（25公斤）以下的飞机）的设计、适航性，以及民航局（CAA）的后续操作应用。 1.2 预计打算在人口稠密地区的受控空域中运行的更大/更高能量SUA设计的制造商和开发商将采用许多现有的载人飞机标准。其中包括SAE ARP4754A和ARP4761等标准，这些标准规定了“安全设计”自上而下的设计方法，以确保sUAS设计能够合理地满足更严格的定性和定量安全要求。然而，ORA对于所有风险状况保持不变，并将成为任何sUAS操作的一部分。 1.3 在减轻和预防事件和事故时，人们通常不会寻求造成损害或伤害他人，因此，恶意行为不在本惯例的范围内。 1.4 作为ORA的一部分，申请人应清楚地理解并能够清楚地阐述其预期任务，以评估安全性并向监管机构提供信息。sUAS操作（任务或一组任务）的文档是许多人所称的操作概念（CONOPS）。 1.5 本规程主要针对寻求其各自CAA适航或运行批准或认证的sUAS申请人，尽管sUAS制造商可能会考虑本规程以及其他系统安全设计标准，以确定缓解危险所需的sUAS设计和运行要求。 1.6 单位- 以英寸-磅为单位的数值应视为标准值。括号中给出的值是到国际单位制的数学转换，仅供参考，不被视为标准值。 1.7 本标准并非旨在解决与其使用相关的所有安全问题（如有）。 本标准的用户有责任在使用前制定适当的安全和健康实践，并确定监管限制的适用性。 ====意义和用途====== 5.1 使用- 本规程旨在供希望进入其各自CAA规定的国家或国际空域的各方使用，用于车辆设计（适航性）或车辆使用（运行批准）。在本实践中，我们认识到复杂程度、风险评估需求和尽职调查的不同，应在CAA和申请人之间的持续对话中确定。在进行ORA之前，用户应该考虑他们的需求、ORA的服务目的以及他们的风险接受程度。使用本惯例并不排除其他识别危险条件或评估和缓解相关风险的举措或过程。 5.2 风险降低，而不是消除- 任何ORA都无法消除与运营相关的所有风险或不确定性。根据本惯例准备ORA旨在降低但不一定完全消除系统复杂性最低的操作风险，该操作在风险较低的环境中进行，并且对人员或财产（尽管存在）造成伤害的可能性降低到可接受的水平。随着任务复杂性的增加，作战环境的风险承受能力可能会降低。例如，随着与飞机相关的动能增加，可能需要更复杂的评估/分析工具和更长的时间来进行ORA。

1.1 This practice focuses on preparing operational risk assessments (ORAs) to be used for supporting small unmanned aircraft systems (sUAS) (aircraft under 55 lb (25 kg)) design, airworthiness, and subsequent operational applications to the civil aviation authority (CAA). 1.2 It is expected that manufacturers and developers of larger/higher energy sUAS designs, intended to operate in controlled airspace over populated areas, will adopt many of the existing manned aircraft standards in use. These include standards such as SAE ARP4754A and ARP4761, which prescribe a “design for safety” top-down design approach to ensure the sUAS designs can reasonably meet more stringent qualitative and quantitative safety requirements. The ORA, however, remains the same for all risk profiles and will be a part of any sUAS operation. 1.3 In mitigating and preventing incidents and accidents, it is understood that people generally do not seek to cause damage or injure others, and therefore, malicious acts are beyond the scope of this practice. 1.4 As part of the ORA, the applicant should clearly understand and be able to articulate their intended mission for purposes of assessing safety and providing information to regulators. This documentation of a sUAS operation (mission, or set of missions) is what many refer to as a concept of operations (CONOPS). 1.5 This practice is intended primarily for sUAS applicants seeking approval or certification for airworthiness or operations from their respective CAA, though sUAS manufacturers may consider this practice, along with other system safety design standards, as appropriate to identify sUAS design and operational requirements needed to mitigate hazards. 1.6 Units— The values stated in inch-pound units are to be regarded as the standard. The values given in parentheses are mathematical conversions to SI units that are provided for information only and are not considered standard. 1.7 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use. ====== Significance And Use ====== 5.1 Use— This practice is intended for use by parties who desire access to the national, or international, airspace as regulated by their respective CAA(s) either for a vehicle design (airworthiness) or a vehicle’s use (operational approval). In this practice, it is recognized the varying levels of complexity, need for risk assessment(s), and due diligence that should be determined in an ongoing dialogue between the CAA and the applicant. Users should consider their requirements, the purpose that the ORA is to serve, and their risk acceptance level before undertaking the ORA. Use of this practice does not preclude other initiatives or processes to identify hazardous conditions or assess and mitigate associated risks. 5.2 Risk Reduced, not Eliminated— No ORA can eliminate all risk or uncertainty with regard to operations. Preparation of an ORA in accordance with this practice is intended to reduce, but may not necessarily completely eliminate, the risk of an operation in which system complexity is minimal, the operation is conducted in a lower risk environment, and the likelihood for harm to people or property, though present, is reduced to an acceptable level. As mission complexity increases, the operational environment may become less risk tolerant. For example, as the kinetic energy associated with the aircraft increases, more complex assessment/analysis tools and greater time may be required to conduct the ORA.