(a) This subpart F contains requirements that an applicant must meet to obtain a safety approval when applying for a license to launch an expendable launch vehicle from a non-Federal launch site. This subpart also contains administrative requirements for a safety review, such as when and how an applicant files the required information, and the requirements for the form and content of each submission.

(b) The requirements of this subpart apply to both orbital and suborbital expendable launch vehicles.

(c) An applicant must demonstrate, through the material filed with the FAA, its ability to comply with the requirements of part 417 of this chapter. To facilitate production of the information required by this subpart, an applicant should become familiar with the requirements of part 417 of this chapter.

(d) For a launch from an exclusive use launch site, where there is no licensed launch site operator, a launch operator must satisfy the requirements of this part and the public safety application requirements of part 420 of this chapter.

For the purposes of this subpart, the definitions of § § 417.3 and 401.5 of this chapter apply.

(a) The FAA conducts a safety review to determine whether an applicant is capable of conducting launch processing and flight without jeopardizing public health and safety and safety of property. The FAA issues a safety approval to a license applicant if the applicant satisfies the requirements of this subpart and demonstrates that it will meet the safety responsibilities and requirements of part 417 of this chapter.

(b) The FAA advises an applicant, in writing, of any issue raised during a safety review that would impede issuance of a safety approval. The applicant may respond, in writing, or amend its license application as required by § 413.17 of this chapter.

(c) An applicant must make available to the FAA upon request a copy of any information incorporated into a license application by reference.

(d) A safety approval is part of the licensing record on which the FAA bases its licensing determination.

(a) An applicant must participate in a pre-application consultation meeting, as required by § 413.5 of this chapter, prior to an applicant's preparation of the initial flight safety analysis required by § 415.115.

(b) At a pre-application consultation meeting, an applicant must provide as complete a description of the planned launch or series of launches as available at the time. An applicant must provide the FAA the following information:

(1) Launch vehicle. Description of:

(i) Launch vehicle;

(ii) Any flight termination system; and

(iii) All hazards associated with the launch vehicle and any payload, including the type and amounts of all propellants, explosives, toxic materials and any radionuclides.

(2) Proposed mission. (i) For an applicant applying for a launch specific license under § 415.3(a), the apogee, perigee, and inclination of any orbital objects and each impact location of any stage or other component.

(ii) For an applicant applying for a launch operator license under § 415.3(b), the planned range of trajectories and flight azimuths, and the range of apogees, perigees, and inclinations of any orbital objects and each impact location of any stage or other component.

(3) Potential launch site. (i) Name and location of the proposed launch site, including latitude and longitude of the proposed launch point;

(ii) Identity of any launch site operator of that site; and

(iii) Identification of any facilities at the launch site that will be used for launch processing and flight.

(a) An applicant must file a safety review document that contains all the information required by §§ 415.109—415.133. An applicant must file the information for a safety review document as required by the outline in appendix B of this part. An applicant must file a sufficiently complete safety review document, except for the ground safety analysis report, no later than six months before the applicant brings any launch vehicle to the proposed launch site.

(b) A launch operator's safety review document must:

(1) Contain a glossary of unique terms and acronyms used in alphabetical order;

(2) Contain a listing of all referenced standards, codes, and publications;

(3) Be logically organized, with a clear and consistent page numbering system and must identify cross-referenced topics;

(4) Use equations and mathematical relationships derived from or referenced to a recognized standard or text, and must define all algebraic parameters;

(5) Include the units of all numerical values provided; and

(6) Include a legend or key that identifies all symbols used for any schematic diagrams.

(c) An applicant's safety review document may include sections not required by appendix B of this part. An applicant must identify each added section by using the word “added” in front of the title of the section. In the first paragraph of the section, an applicant must explain any addition to the outline in appendix B of this part.

(d) If a safety review document section required by appendix B of this part does not apply to an applicant's proposed launch, an applicant must identify the sections in the application by the words “not applicable” preceding the title of the section. In the first paragraph of the section, an applicant must describe and justify why the section does not apply.

(e) An applicant may reference documentation previously filed with the FAA.

An applicant's safety review document must contain the following information:

(a) Launch site description. An applicant must identify the proposed launch site and include the following:

(1) Boundaries of the launch site;

(2) Launch point location, including latitude and longitude;

(3) Identity of any launch site operator of that proposed site; and

(4) Identification of any facilities at the launch site that will be used for launch processing and flight.

(b) Launch vehicle description. An applicant must provide the following:

(1) A written description of the launch vehicle. The description must include a table specifying the type and quantities of all hazardous materials on the launch vehicle and must include propellants, explosives, and toxic materials; and

(2) A drawing of the launch vehicle that identifies:

(i) Each stage, including strap-on motors;

(ii) Physical dimensions and weight;

(iii) Location of all safety critical systems, including any flight termination hardware, tracking aids, or telemetry systems;

(iv) Location of all major launch vehicle control systems, propulsion systems, pressure vessels, and any other hardware that contains potential hazardous energy or hazardous material; and

(v) For an unguided suborbital launch vehicle, the location of the rocket's center of pressure in relation to its center of gravity for the entire flight profile.

(c) Payload description. An applicant must include or reference documentation previously filed with the FAA that contains the payload information required by § 415.59 for any payload or class of payload.

(d) Trajectory. An applicant must provide two drawings depicting trajectory information. An applicant must file additional trajectory information as part of the flight safety analysis data required by § 415.115.

(1) One drawing must depict the proposed nominal flight profile with downrange depicted on the abscissa and altitude depicted on the ordinate axis. The nominal flight profile must be labeled to show each planned staging event and its time after liftoff from launch through orbital insertion or final impact; and

(2) The second drawing must depict instantaneous impact point ground traces for each of the nominal trajectory, the three-sigma left lateral trajectory and the three-sigma right lateral trajectory determined under § 417.207 of this chapter. The trajectories must be depicted on a latitude/longitude grid, and the grid must include the outlines of any continents and islands.

(e) Staging events. An applicant must provide a table of nominal and ±three-sigma times for each major staging event and must describe each event, including the predicted impact point and dispersion of each spent stage.

(f) Vehicle performance graphs. An applicant must provide graphs of the nominal and ±three-sigma values as a function of time after liftoff for the following launch vehicle performance parameters: thrust, altitude, velocity, instantaneous impact point arc-range measured from the launch point, and present position arc-range measured from the launch point.

An applicant's safety review document must contain organizational charts and a description that shows that the launch operator's organization satisfies the requirements of § 417.103 of this chapter. An applicant's safety review document must also identify all persons with whom the applicant has contracted to provide safety-related goods or services for the launch of the launch vehicle.

(a) A safety review document must describe how the applicant will satisfy the personnel certification program requirements of § 417.105 of this chapter and identify by position those individuals who implement the program.

(b) An applicant's safety review document must contain a copy of its documentation that demonstrates how the launch operator implements the personnel certification program.

(c) An applicant's safety review document must contain a table listing each hazardous operation or safety critical task that certified personnel must perform. For each task, the table must identify by position the individual who reviews personnel qualifications and certifies personnel for performing the task.

(a) Flight safety analysis. An applicant's safety review document must describe each analysis method employed to meet the flight safety analysis requirements of part 417, subpart C, of this chapter. An applicant's safety review document must demonstrate how each analysis method satisfies the flight safety analysis requirements of part 417, subpart C, of this chapter. An applicant's safety review document must contain analysis products and other data that demonstrate the applicant's ability to meet the public risk criteria of § 417.107 of this chapter and to establish launch safety rules as required by § 417.113 of this chapter. An applicant's flight safety analysis must satisfy the following requirements:

(1) An applicant must file the proposed flight safety analysis methodology and the preliminary flight safety analysis products no later than 18 months for any orbital or guided suborbital launch vehicle, and nine months for any unguided suborbital launch vehicle, prior to bringing any launch vehicle to the proposed launch site.

(2) For a launch operator license, an applicant must file flight safety analysis products that account for the range of launch vehicles and flight trajectories applied for, or the worst case vehicle and trajectory under which flight will be attempted, no later than 6 months before the applicant brings any launch vehicle to the proposed launch site. For a launch specific license, an applicant must file flight safety analysis products that account for the actual flight conditions, no later than 6 months before the applicant brings any launch vehicle to the proposed launch site.

(3) The flight safety analysis performed by an applicant must be completed as required by subpart C of part 417 of this chapter. An applicant may identify those portions of the analysis that it expects to refine as the first proposed flight date approaches. An applicant must identify any analysis product subject to change, describe what needs to be done to finalize the product, and identify when before flight it will be finalized. If a license allows more than one launch, an applicant must demonstrate the applicability of the analysis methods to each of the proposed launches and identify any expected differences in the flight safety analysis methods among the proposed launches. Once licensed, a launch operator must perform a flight safety analysis for each launch using final launch vehicle performance and other data as required by subpart C of part 417 of this chapter and using the analysis methods approved by the FAA through the licensing process.

(b) Radionuclides. An applicant's safety review document must identify the type and quantity of any radionuclide on a launch vehicle or payload. For each radionuclide, an applicant must include a reference list of all documentation addressing the safety of its intended use and describe all approvals by the Nuclear Regulatory Commission for launch processing. An applicant must provide radionuclide information to the FAA at the pre-application consultation as required by § 415.105. The FAA will evaluate launch of any radionuclide on a case-by-case basis, and issue an approval if the FAA finds that the launch is consistent with public health and safety.

(c) Flight safety plan. An applicant's safety review document must contain a flight safety plan that satisfies § 417.111(b) of this chapter. The plan need not be restricted to public safety related issues and may combine other flight safety issues as well, such as employee safety, so as to be all-inclusive.

(d) Natural and triggered lightning. For any orbital or guided suborbital expendable launch vehicle, an applicant must demonstrate that it will satisfy the flight commit criteria of § 417.113(c) of this chapter and appendix G of part 417 of this chapter for natural and triggered lightning. If an applicant's safety review document states that any flight commit criterion that is otherwise required by appendix G of part 417 of this chapter does not apply to a proposed launch or series of launches, the applicant's safety review document must demonstrate that the criterion does not apply.

(a) General. An applicant's safety review document must include a ground safety analysis report, and a ground safety plan for its launch processing and post-flight operations as required by this section, § 417.109 of this chapter, and subpart E of part 417 of this chapter when launching from a launch point in the United States. Launch processing and post-launch operations at a launch point outside the United States may be subject to the requirements of the governing jurisdiction.

(b) Ground safety analysis. A ground safety analysis must review each system and operation used in launch processing and post-flight operations as required by § 417.109 of this chapter, and subpart E of part 417 of this chapter.

(1) An applicant must file an initial ground safety analysis report no later than 12 months for any orbital or guided suborbital launch vehicle, and nine months for an unguided suborbital launch vehicle, before the applicant brings any launch vehicle to the proposed launch site. An initial ground safety analysis report must be in a proposed final or near final form and identify any incomplete items. An applicant must document any incomplete items and track them to completion. An applicant must resolve any FAA comments on the initial report and file a complete ground safety analysis report, no later than two months before the applicant brings any launch vehicle to the proposed launch site. Furthermore, an applicant must keep its ground safety analysis report current. Any late developing change to a ground safety analysis report must be coordinated with the FAA as an application amendment as required by § 413.17 of this chapter as soon as the applicant identifies the need for a change.

(2) An applicant must file a ground safety analysis report that satisfies the ground safety analysis requirements of § 417.109 of this chapter, and subpart E of part 417 of this chapter.

(3) The person designated under § 417.103(b)(1) of this chapter and the person designated under § 417.103(b)(2) of this chapter must approve and sign the ground safety analysis report.

(c) Ground safety plan. An applicant's safety review document must contain a ground safety plan that satisfies § 417.111(c) of this chapter. The applicant must file this plan with the FAA no later than six months prior to bringing the launch vehicle to the proposed launch site. This ground safety plan must describe implementation of the hazard controls identified by an applicant's ground safety analysis and implementation of the ground safety requirements of subpart E of part 417 of this chapter. A ground safety plan must address all public safety related issues and may include other ground safety issues if an applicant intends it to have a broader scope.

An applicant's safety review document must contain the plans required by § 417.111 of this chapter, except for the countdown plan of § 417.111(l) of this chapter. An applicant's launch plans do not have to be separate documents, and may be part of other applicant documentation. An applicant must incorporate each launch safety rule established under § 417.113 of this chapter into a related launch safety plan.

An applicant's safety review document must contain a generic launch processing schedule that identifies each review, rehearsal, and safety critical preflight operation to be conducted as required by §§ 417.117, 417.119, and 417.121 of this chapter. The launch schedule must also identify day of flight activities. The launch processing schedule must show each of these activities referenced to liftoff, such as liftoff minus three days.

(a) An applicant's safety review document must describe all computing systems and software that perform a safety-critical computer system function for any operation performed during launch processing or flight that could have a hazardous effect on the public as required by § 417.123 of this chapter.

(b) An applicant's safety review document must list and describe all safety-critical computer system functions involved in a proposed launch, including associated hardware and software interfaces. For each system with a safety-critical computer system function, an applicant's safety review document must:

(1) Describe all safety-critical computer system functions, including each safety-critical interface with any other system;

(2) Describe all systems, including all hardware and software, and the layout of each operator console and display;

(3) Provide flow charts or diagrams that show all hardware data busses, hardware interfaces, software interfaces, data flow, and power systems, and all operations of each safety-critical computer system function;

(4) Provide all logic diagrams and software designs;

(5) List all operator user manuals and documentation by title and date;

(6) Describe the computing system and software system safety process as required by § 417.123(a).

(7) Provide all results of computing system and software hazard analyses as required by § 417.123(c).

(8) Provide all plans and results of computing systems and software validation and verification as required by § 417.123(d).

(9) Provide all plans for software development as required by § 417.123(e).

An applicant's safety review document must identify any public safety-related policy, requirement, or practice that is unique to the proposed launch, or series of launches, as required by § 417.127 of this chapter. An applicant's safety review document must describe how each unique safety policy, requirement, or practice ensures the safety of the public.

(a) General. This part applies to an applicant launching an orbital or guided sub-orbital expendable launch vehicle that uses a flight safety system to protect public safety as required by § 417.107(a) of this chapter. An applicant's safety review document must contain the flight safety system data identified by this section. The applicant must file all data required by this section no later than 18 months before bringing any launch vehicle to a proposed launch site.

(b) Flight safety system description. A safety review document must describe an applicant's flight safety system and its operation. Part 417, subpart D of this chapter and appendices D, E, and F of part 417 of this chapter contain the flight safety system and subsystems design and operational requirements.

(c) Flight safety system diagram. An applicant's safety review document must contain a block diagram that identifies all flight safety system subsystems. The diagram must include the following subsystems defined in part 417, subpart D of this chapter: flight termination system; command control system; tracking; telemetry; communications; flight safety data processing, display, and recording system; and flight safety official console.

(d) Subsystem design information. An applicant's safety review document must contain all of the following data that applies to each subsystem identified in the block diagram required by paragraph (c) of this section:

(1) Subsystem description. A physical description of each subsystem and its components, its operation, and interfaces with other systems or subsystems.

(2) Subsystem diagram. A physical and functional diagram of each subsystem, including interfaces with other systems and subsystems.

(3) Component location. Drawings showing the location of all subsystem components, and the details of the mounting arrangements, as installed on the vehicle, and at the launch site.

(4) Electronic components. A physical description of each subsystem electronic component, including operating parameters and functions at the system and piece-part level. An applicant must also provide the name of the manufacturer and any model number of each component and identify whether the component is custom designed and built or off-the-shelf-equipment.

(5) Mechanical components. An illustrated parts breakdown of all mechanically operated components for each subsystem, including the name of the manufacturer and any model number.

(6) Subsystem compatibility. A demonstration of the compatibility of the onboard launch vehicle flight termination system with the command control system.

(7) Flight termination system component storage, operating, and service life. A listing of all flight termination system components that have a critical storage, operating, or service life and a summary of the applicant's procedures for ensuring that each component does not exceed its storage, operating, or service life before flight.

(8) Flight termination system element location. For a flight termination system, a description of where each subsystem element is located, where cables are routed, and identification of mounting attach points and access points.

(9) Flight termination system electrical connectors and connections and wiring diagrams and schematics. For a flight termination system, a description of all subsystem electrical connectors and connections, and any electrical isolation. The safety review document must also contain flight termination system wiring diagrams and schematics and identify the test points used for integrated testing and checkout.

(10) Flight termination system batteries. A description of each flight termination system battery and cell, the name of the battery or cell manufacturer, and any model numbers.

(11) Controls and displays. For a flight safety official console, a description of all controls, displays, and charts depicting how real time vehicle data and flight safety limits are displayed. The description must identify the scales used for displays and charts.

(e) System analyses. An applicant must perform the reliability and other system analyses for a flight termination system and command control system of § 417.309 of this chapter. An applicant's safety review document must contain the results of each analysis.

(f) Environmental design. An applicant must determine the flight termination system maximum predicted environment levels required by section D417.7 of appendix D of part 417 of this chapter, and the design environments and design margins of section D417.3 of appendix D of part 417 of this chapter. An applicant's safety review document must summarize the analyses and measurements used to derive the maximum predicted environment levels. The safety review document must contain a matrix that identifies the maximum predicted environment levels and the design environments.

(g) Flight safety system compliance matrix. An applicant's safety review document must contain a compliance matrix of the function, reliability, system, subsystem, and component requirements of part 417 of this chapter and appendix D of part 417 of this chapter. This matrix must identify each requirement and indicate compliance as follows:

(1) “Yes” if the applicant's system meets the requirement of part 417 of this chapter. The matrix must reference documentation that demonstrates compliance;

(2) “Not applicable” if the applicant's system design and operational environment are such that the requirement does not apply. For each such case, the applicant must demonstrate, in accordance with section 406.3(b), the non-applicability of that requirement as an attachment to the matrix; or

(3) “Equivalent level of safety” in each case where the applicant proposes to show that its system provides an equivalent level of safety through some means other than that required by part 417 of this chapter. For each such case, an applicant must clearly and convincingly demonstrate, as required by § 406.3(b), through a technical rationale within the matrix, or as an attachment, that the proposed alternative provides a level of safety equivalent to satisfying the requirement that it would replace.

(h) Flight termination system installation procedures. An applicant's safety review document must contain a list of the flight termination system installation procedures and a synopsis of the procedures that demonstrates how each of those procedures meet the requirements of section D417.15 of appendix D of part 417 of this chapter. The list must reference each procedure by title, any document number, and date.

(i) Tracking validation procedures. An applicant's safety review document must contain the procedures identified by § 417.121(h) of this chapter for validating the accuracy of the launch vehicle tracking data supplied to the flight safety crew.

(a) General. An applicant's safety review document must contain the flight safety system test data required by this section for the launch of an orbital and guided suborbital expendable launch vehicle that uses a flight safety system to protect public safety as required by § 417.107(a) of this chapter. This section applies to all testing required by part 417, subpart D of this chapter and its appendices, including qualification, acceptance, age surveillance, and preflight testing of a flight safety system and its subsystems and individual components. An applicant must file all required test data, no later than 12 months before the applicant brings any launch vehicle to the proposed launch site. An applicant may file test data earlier to allow greater time for addressing issues that the FAA may identify to avoid possible impact on the proposed launch date. Flight safety system testing need not be completed before the FAA issues a launch license. Prior to flight, a licensee must successfully complete all required flight safety system testing and file the completed test reports or the test report summaries required by § 417.305(d) of this chapter and section E417.1(i) of appendix E of part 417 of this chapter.

(b) Testing compliance matrix. An applicant's safety review document must contain a compliance matrix of all the flight safety system, subsystem, and component testing requirements of part 417 of this chapter and appendix E to part 417 of this chapter. This matrix must identify each test requirement and indicate compliance as follows:

(1) “Yes” if the applicant performs the system or component testing required by part 417 of this chapter. The matrix must reference documentation that demonstrates compliance;

(2) “Not applicable” if the applicant's system design and operational environment are such that the test requirement does not apply. For each such case, an applicant must demonstrate, as required by § 406.3(b), of the non-applicability of that requirement as an attachment to the matrix;

(3) “Similarity” if the test requirement applies to a component whose design is similar to a previously qualified component. For each such case, an applicant must demonstrate similarity by performing the analysis required by appendix E of part 417 of this chapter. The matrix, or an attachment, must contain the results of each analysis; or

(4) “Equivalent level of safety” in each case where the applicant proposes to show that its test program provides an equivalent level of safety through some means other than that required by part 417 of this chapter. For each such case, an applicant must clearly and convincingly demonstrate through a technical rationale, within the matrix or as an attachment, that the alternative provides a level of safety equivalent to satisfying the requirement that it replaces, as required by § 406.3(c).

(c) Test program overview and schedule. A safety review document must contain a summary of the applicant's flight safety system test program that identifies the location of the testing and the personnel who ensure the validity of the results. A safety review document must contain a schedule for successfully completing each test before flight. The applicant must reference the schedule to the time of liftoff for the first proposed flight attempt.

(d) Flight safety system test plans and procedures. An applicant's safety review document must contain test plans that satisfy the flight safety system testing requirements of subpart D of part 417 of this chapter and appendix E of part 417 of this chapter. An applicant's safety review document must contain a list of all flight termination system test procedures and a synopsis of the procedures that demonstrates how they meet the test requirements of part 417 of this chapter. The list must reference each procedure by title, any document number, and date.

(e) Test reports. An applicant's safety review document must contain either the test reports, or a summary of the test report which captures the overall test results, including all test discrepancies and their resolution, prepared as required by § 417.305(d) of this chapter and section E417.1(i) of appendix E of part 417 of this chapter, for each flight safety system test completed at the time of license application. An applicant must file any remaining test reports or summaries before flight as required by § 417.305(d) and section E417.1(i) of appendix E of part 417 of this chapter. Upon request, the launch operator must file the complete test report with the FAA for review, if the launch operator previously filed test report summaries with the FAA.

(f) Reuse of flight termination system components. An applicant's safety review document must contain a reuse qualification test, refurbishment plan, and acceptance test plan for the use of any flight termination system component on more than one flight. This test plan must define the applicant's process for demonstrating that the component can satisfy all its performance specifications when subjected to the qualification test environmental levels plus the total number of exposures to the maximum expected environmental levels for each of the flights to be flown.

(a) An applicant's safety review document must identify each flight safety system crew position and the role of that crewmember during launch processing and flight of a launch vehicle.

(b) An applicant's safety review document must describe the certification program for flight safety system crewmembers established to ensure compliance with §§ 417.105 and 417.311 of this chapter.

An applicant must demonstrate compliance with § 417.129 of this chapter, for any proposed launch of a launch vehicle with a stage or component that will reach Earth orbit.

The FAA notifies an applicant, in writing, if it has denied safety approval for a license application. The notice states the reasons for the FAA's determination. The applicant may respond to the reasons for the determination and request reconsideration.