US LAWS, STATUTES & CODES ON-LINE

(a) The distance from any proposed launch point to the closest launch site boundary must be at least as great as the debris dispersion radius of the largest launch vehicle type and weight class proposed for the launch point.

(b) For a launch site supporting any expendable launch vehicle, an applicant shall use the largest distance provided by table 2 for the type and weight class of any launch vehicle proposed for the launch point.

(c) For a launch site supporting any reusable launch vehicle, an applicant shall determine the debris dispersion radius that represents the maximum distance from a launch point that debris travels given a worst-case launch vehicle failure in the launch area. An applicant must clearly and convincingly demonstrate the validity of its proposed debris dispersion radius.

(a) Guided orbital expendable launch vehicle. For a guided orbital expendable launch vehicle, an applicant shall define a flight corridor that:

(1) Encompasses an area that the applicant estimates, in accordance with the requirements of this part, to contain debris with a ballistic coefficient of ≥ 3 pounds per square foot, from any non-nominal flight of a guided orbital expendable launch vehicle from the launch point to a point 5000 nm downrange, or where the IIP leaves the surface of the Earth, whichever is shorter;

(2) Includes an overflight exclusion zone where the public risk criteria of 30×10⁻⁶ would be exceeded if one person were present in the open; and

(3) Uses one of the methodologies provided in appendix A or B of this part. The FAA will approve an alternate method if an applicant provides a clear and convincing demonstration that its proposed method provides an equivalent level of safety to that required by appendix A or B of this part.

(b) Guided sub-orbital expendable launch vehicle. For a guided sub-orbital expendable launch vehicle, an applicant shall define a flight corridor that:

(1) Encompasses an area that the applicant estimates, in accordance with the requirements of this part, to contain debris with a ballistic coefficient of ≥ 3 pounds per square foot, from any non-nominal flight of a guided sub-orbital expendable launch vehicle from the launch point to impact with the earth's surface;

(2) Includes an impact dispersion area for the launch vehicle's last stage;

(3) Includes an overflight exclusion zone where the public risk criteria of 30×10⁻⁶ would be exceeded if one person were present in the open; and

(4) Uses one of the methodologies provided in appendices A or B to this part. The FAA will approve an alternate method if an applicant provides a clear and convincing demonstration that its proposed method provides an equivalent level of safety to that required by appendix A or B of this part.

(c) Unguided sub-orbital expendable launch vehicle. (1) For an unguided sub-orbital expendable launch vehicle, an applicant shall define the following using the methodology provided by appendix D of this part:

(i) Impact dispersion areas that the applicant estimates, in accordance with the requirements of this part, to contain the impact of launch vehicle stages from nominal flight of an unguided sub-orbital expendable launch vehicle from the launch point to impact with the earth's surface; and

(ii) An overflight exclusion zone where the public risk criteria of 30×10⁻⁶ would be exceeded if one person were present in the open.

(2) The FAA will approve an alternate method if an applicant provides a clear and convincing demonstration that its proposed method provides an equivalent level of safety to that required by appendix D of this part.

(3) An applicant shall base its analysis on an unguided suborbital launch vehicle whose final launch vehicle stage apogee represents the intended use of the launch point.

(d) Reusable launch vehicle. For a reusable launch vehicle, an applicant shall define a flight corridor that contains the hazardous debris from nominal and non-nominal flight of a reusable launch vehicle. The applicant must provide a clear and convincing demonstration of the validity of its flight corridor.

(a) If a flight corridor or impact dispersion area defined by section 420.23 contains a populated area, the applicant shall estimate the casualty expectation associated with the flight corridor or impact dispersion area. An applicant shall use the methodology provided in appendix C to this part for guided orbital or suborbital expendable launch vehicles and appendix D for unguided suborbital launch vehicles. The FAA will approve an alternate method if an applicant provides a clear and convincing demonstration that its proposed method provides an equivalent level of safety to that required by appendix C or D of this part. For a reusable launch vehicle, an applicant must provide a clear and convincing demonstration of the validity of its risk analysis.

(b) If the estimated expected casualty exceeds 30×10⁻⁶, the FAA will not approve the location of the proposed launch point.

An applicant shall provide the following launch site location review information in its application:

(a) A map or maps showing the location of each launch point proposed, and the flight azimuth, IIP, flight corridor, and each impact range and impact dispersion area for each launch point;

(b) Each launch vehicle type and any launch vehicle class proposed for each launch point;

(c) Trajectory data;

(d) Wind data, including each month and any percent wind data used in the analysis;

(e) Any launch vehicle apogee used in the analysis;

(f) Each populated area located within a flight corridor or impact dispersion area;

(g) The estimated casualty expectancy calculated for each populated area within a flight corridor or impact dispersion area;

(h) The effective casualty areas used in the analysis;

(i) The estimated casualty expectancy for each flight corridor or set of impact dispersion areas; and

(j) If populated areas are located within an overflight exclusion zone, a demonstration that there are times when the public is not present or that the applicant has an agreement in place to evacuate the public from the overflight exclusion zone during a launch.

An applicant for a license to operate a launch site for an unproven launch vehicle shall provide a clear and convincing demonstration that its proposed launch site location provides an equivalent level of safety to that required by this part.

(a) Except as provided by paragraph (c) of this section, an applicant shall complete an agreement with the local U.S. Coast Guard district to establish procedures for the issuance of a Notice to Mariners prior to a launch and other such measures as the Coast Guard deems necessary to protect public health and safety.

(b) Except as provided by paragraph (c) of this section, an applicant shall complete an agreement with the FAA Air Traffic Control (ATC) office having jurisdiction over the airspace through which launches will take place, to establish procedures for the issuance of a Notice to Airmen prior to a launch and for closing of air routes during the launch window and other such measures as the FAA ATC office deems necessary to protect public health and safety.

(c) An applicant that plans to operate a launch site located on a federal launch range does not have to comply with section 420.31 if the applicant is using existing federal launch range agreements with the U.S. Coast Guard and the FAA ATC office having jurisdiction over the airspace through which launches will take place.

(a) A license to operate a launch site authorizes a licensee to operate a launch site in accordance with the representations contained in the licensee's application, with terms and conditions contained in any license order accompanying the license, and subject to the licensee's compliance with 49 U.S.C. subtitle IX, ch. 701 and this chapter.

(b) A license to operate a launch site authorizes a licensee to offer its launch site to a launch operator for each launch point for the type and any weight class of launch vehicle identified in the license application and upon which the licensing determination is based.

(c) Issuance of a license to operate a launch site does not relieve a licensee of its obligation to comply with any other laws or regulations; nor does it confer any proprietary, property, or exclusive right in the use of airspace or outer space.

A license to operate a launch site remains in effect for five years from the date of issuance unless surrendered, suspended, or revoked before the expiration of the term and is renewable upon application by the licensee.

(a) Only the FAA may transfer a license to operate a launch site.

(b) The FAA will transfer a license to an applicant who has submitted an application in accordance with 14 CFR part 413, satisfied the requirements of §420.15, and obtained each approval required by §420.17 for a license.

(c) The FAA may incorporate by reference any findings made part of the record that supported a prior related licensing determination.

(a) Upon application or upon its own initiative, the FAA may modify a license to operate a launch site at any time by issuing a license order that adds, removes, or modifies a license term or condition to ensure compliance with the Act and the requirements of this chapter.

(b) After a license to operate a launch site has been issued, a licensee shall apply to the FAA for modification of its license if:

(1) The licensee proposes to operate the launch site in a manner that is not authorized by the license; or

(2) The licensee proposes to operate the launch site in a manner that would make any representation contained in the license application that is material to public health and safety or safety of property no longer accurate and complete.

(c) An application to modify a license shall be prepared and submitted in accordance with part 413 of this chapter. The licensee shall indicate any part of its license or license application that would be changed or affected by a proposed modification.

(d) The FAA approves a modification request that satisfies the requirements of this part.

(e) Upon approval of a license modification, the FAA issues either a written approval to the licensee or a license order modifying the license if a stated term or condition of the license is changed, added, or deleted. A written approval has the full force and effect of a license order and is part of the licensing record.

A licensee shall allow access by and cooperate with federal officers or employees or other individuals authorized by the FAA to observe any activities of the licensee, its customers, its contractors, or subcontractors, associated with licensed operation of the licensee's launch site.

(a) A licensee shall operate its launch site in accordance with the representations in the application upon which the licensing determination is based.

(b) A licensee is responsible for compliance with 49 U.S.C. Subtitle IX, ch. 701 and for meeting the requirements of this chapter.

(a) A licensee shall prevent unauthorized access to the launch site, and unauthorized, unescorted access to explosive hazard facilities or other hazard areas not otherwise controlled by a launch operator, through the use of security personnel, surveillance systems, physical barriers, or other means approved as part of the licensing process.

(b) A licensee shall notify anyone entering the launch site of safety rules and emergency and evacuation procedures prior to that person's entry unless that person has received a briefing on those rules and procedures within the previous year.

(c) A licensee shall employ warning signals or alarms to notify any persons at the launch site of any emergency.

(a) A licensee shall develop and implement procedures to schedule operations to ensure that each operation carried out by a customer at the launch site does not create the potential for a mishap that could result in harm to the public because of the proximity of the operations, in time or place, to operations of any other customer. A customer includes any launch operator, and any contractor, subcontractor or customer of the launch site operator's customer at the launch site.

(b) A licensee shall provide its launch site scheduling requirements to each customer before the customer begins operations at the launch site.

(a) A licensee shall notify each launch operator and any other customer of any limitations on the use of the launch site. A licensee shall also communicate limitations on the use of facilities provided to customers by the launch site operator.

(b) A licensee shall maintain its agreement, made in accordance with §420.31(a), with the local U.S. Coast Guard district.

(c) A licensee shall maintain its agreement, made in accordance with §420.31(b), with the FAA ATC office having jurisdiction over the airspace through which launches will take place.

(d) At least two days prior to flight of a launch vehicle, the licensee shall notify local officials and all owners of land adjacent to the launch site of the flight schedule.

(a) General. A licensee shall develop and implement a launch site accident investigation plan that contains the licensee's procedures for reporting, responding to, and investigating launch site accidents, as defined by §420.5, and for cooperating with federal officials in case of a launch accident. The launch site accident investigation plan must be signed by an individual authorized to sign and certify the application in accordance with §413.7(c) of this chapter.

(b) Reporting requirements. A launch site accident investigation plan shall provide for—

(1) Immediate notification to the Federal Aviation Administration (FAA) Washington Operations Center in the event of a launch site accident.

(2) Submission of a written preliminary report to the FAA, Associate Administrator for Commercial Space Transportation, within five days of any launch site accident. The report must include the following information:

(i) Date and time of occurrence;

(ii) Location of the event;

(iii) Description of the event;

(iv) Number of injuries, if any, and general description of types of injuries suffered;

(v) Property damage, if any, and an estimate of its value;

(vi) Identification of hazardous materials, as defined by §401.5 of this chapter, involved in the event;

(vii) Any action taken to contain the consequences of the event; and

(viii) Weather conditions at the time of the event.

(c) Response plan. A launch site accident investigation plan shall contain procedures that—

(1) Ensure the consequences of a launch site accident are contained and minimized;

(2) Ensure data and physical evidence are preserved;

(3) Require the licensee to report to and cooperate with FAA or National Transportation Safety Board (NTSB) investigations and designate one or more points of contact for the FAA or NTSB; and

(4) Require the licensee to identify and adopt preventive measures for avoiding recurrence of the event.

(d) Investigation plan. A launch site accident investigation plan must contain—

(1) Procedures for investigating the cause of a launch site accident;

(2) Procedures for reporting launch site accident investigation results to the FAA; and

(3) Delineated responsibilities, including reporting responsibilities for personnel assigned to conduct investigations and for any one retained by the licensee to conduct or participate in investigations.

(e) Launch accidents. A launch site accident investigation plan shall contain—

(1) Procedures for participating in an investigation of a launch accident for launches launched from the launch site;

(2) Require the licensee to cooperate with FAA or National Transportation Safety Board (NTSB) investigations of a launch accident for launches launched from the launch site.

(f) Applicability of other accident investigation procedures. Accident investigation procedures developed in accordance with 29 CFR 1910.119 and 40 CFR part 68 will satisfy the requirements of paragraphs (c) and (d) of this section to the extent that they include the elements required by paragraphs (c) and (d) of this section.

(a) A licensee shall maintain all records, data, and other material needed to verify that its operations are conducted in accordance with representations contained in the licensee's application. A licensee shall retain records for three years.

(b) In the event of a launch or launch site accident, a licensee shall preserve all records related to the event. Records shall be retained until completion of any federal investigation and the FAA advises the licensee that the records need not be retained.

(c) A licensee shall make available to federal officials for inspection and copying all records required to be maintained under the regulations.

(a) Except as otherwise provided by paragraph (b) of this section, a licensee shall ensure that the configuration of the launch site is in accordance with an explosive site plan, and that the licensee's explosive site plan is in compliance with the requirements of §§420.65–420.69. The explosive site plan shall include:

(1) A scaled map that shows the location of all proposed explosive hazard facilities at the proposed launch site and that shows actual and minimal allowable distances between each explosive hazard facility and all other explosive hazard facilities and each public area, including the launch site boundary;

(2) A listing of the maximum quantities of liquid and solid propellants and other explosives to be located at each explosive hazard facility, including the class and division for each solid explosive and the hazard and compatibility group for each liquid propellant; and

(3) A description of each activity to be conducted in each explosive hazard facility.

(b) A licensee operating a launch site located on a federal launch range does not have to comply with the requirements in §§420.65–420.69 if the licensee is in compliance with the federal launch range's explosive safety requirements.

(c) For explosive siting issues not otherwise addressed by the requirements of §§420.65–420.69, a launch site operator must clearly and convincingly demonstrate a level of safety equivalent to that otherwise required by part 420.

(a) A launch site operator shall determine the maximum total quantity of solid propellants and other solid explosives by class and division, in accordance with 49 CFR part 173, Subpart C, to be located in each explosive hazard facility where solid propellants or other solid explosives will be handled.

(b) When explosive divisions 1.1 and 1.3 explosives are located in the same explosive hazard facility, the total quantity of explosive shall be treated as division 1.1 for quantity-distance determinations; or, a launch site operator may add the net explosive equivalent weight of the division 1.3 items to the net weight of division 1.1 items to determine the total quantity of explosives.

(c) A launch site operator shall separate each explosive hazard facility where solid propellants and other solid explosives are handled from all other explosive hazard facilities, each public area and the launch site boundary by a distance no less than those provided for each quantity and explosive division in appendix E, table E–1.

(d) A launch site operator shall follow the following separation rules:

(1) A launch site operator shall employ no less than the applicable public area distance to separate an explosive hazard facility from each public area and from the launch site boundary.

(2) A launch site operator shall employ no less than an intraline distance to separate an explosive hazard facility from all other explosive hazard facilities used by a single customer.

(3) For explosive division 1.1 only, a launch site operator may employ no less than 60% of the applicable public area distance, or the public traffic route distance, to separate an explosive hazard facility from a public area that consists only of a public highway or railroad line.

(4) A launch site operator may use linear interpolation for NEW quantities between table entries.

(5) A launch site operator shall measure separation distance from the closest debris or explosive hazard source in an explosive hazard facility.

(a) For an explosive hazard facility where liquid propellants are handled or stored, a launch site operator shall determine the total quantity of liquid propellant and, if applicable pursuant to paragraph (a)(3) of this section, the explosive equivalent of liquid propellant in each explosive hazard facility in accordance with the following:

(1) The quantity of liquid propellant in a tank, drum, cylinder, or other container is the net weight in pounds of the propellant in the container. The determination of quantity shall include any liquid propellant in associated piping to any point where positive means are provided for interrupting the flow through the pipe, or interrupting a reaction in the pipe in the event of a mishap.

(2) Where two or more containers of compatible liquid propellants are handled or stored together in an explosive hazard facility, the total quantity of propellant to determine the minimum separation distance between the explosive hazard facility and all other explosive hazard facilities and each public area shall be the total quantity of liquid propellant in all containers, unless:

(i) The containers are separated one from the other by the appropriate distance as provided by paragraph (b)(2) of this section; or

(ii) The containers are subdivided by intervening barriers, such as diking, that prevent mixing.

(iii) If paragraph (a)(2)(i) or (ii) of this section apply, a launch site operator shall use the quantity of propellant requiring the greatest separation distance pursuant to paragraph (b) of this section to determine the minimum separation distance between the explosive hazard facility and all other explosive hazard facilities and each public area.

(3) Where two or more containers of incompatible liquid propellants will be handled or stored together in an explosive hazard facility, a launch site operator shall determine the explosive equivalent in pounds of the combined liquids, using the formulas provided in appendix E, table E–2, to determine the minimum separation distance between the explosive hazard facility and other explosive hazard facilities and public areas unless the containers are separated one from the other by the appropriate distance as determined in paragraph (b)(3) of this section. A launch site operator shall then use the quantity of liquid propellant requiring the greatest separation distance to determine the minimum separation distance between the explosive hazard facility and all other explosive hazard facilities and each public area.

(4) A launch site operator shall convert quantities of liquid propellants from gallons to pounds using the conversion factors provided in appendix E, table E–3 and the following equation:

Pounds of propellant = gallons × density of propellant (pounds per gallon).

(b) A launch site operator shall use appendix E, table E–3 to determine hazard and compatibility groups and shall separate liquid propellants from each other and from each public area using distances no less than those provided in appendix E, tables E–4 through E–7 in accordance with the following:

(1) A launch site operator shall measure minimum separation distances from the hazard source in an explosive hazard facility, such as a container, building, segment, or positive cutoff point in piping, closest to each explosive hazard facility.

(2) A launch site operator shall measure the minimum separation distance between compatible liquid propellants using the “intragroup and compatible” distance for the propellant quantity and hazard group that requires the greater distance prescribed by appendix E, tables E–4, E–5, and E–6.

(3) A launch site operator shall measure the minimum separation distance between liquid propellants of different compatibility groups using the “public area and incompatible” distance for the propellant quantity and hazard group that requires the greater distance provided in appendix E, tables E–4, E–5, and E–6, unless the propellants of different compatibility groups are subdivided by intervening barriers that prevent mixing. If such barriers are present, the minimum separation distance shall be the “intragroup and compatible” distance for the propellant quantity and group that requires the greater distance provided in appendix E, tables E–4, E–5, and E–6.

(4) A launch site operator shall separate liquid propellants from each public area using a distance no less than the “public area and incompatible” distance provided in appendix E, tables E–4, E–5, and E–6.

(5) A launch site operator shall separate each explosive hazard facility that contains liquid propellants where explosive equivalents apply pursuant to paragraph (a)(3) of this section from all other explosive hazard facilities of a single customer using the intraline distance provided in appendix E, table E–7, and from each public area using the public area distance provided in appendix E, table E–7.

(a) A launch site operator proposing an explosive hazard facility where solid and liquid propellants are to be located together shall determine the minimum separation distances between the explosive hazard facility and other explosive hazard facilities and public areas in accordance with one method provided in paragraphs (b), (c), or (d) of this section.

(b) A launch site operator shall determine the minimum separation distances between the explosive hazard facility and all other explosive hazard facilities and public areas required for the liquid propellants in accordance with section 420.67(b)(5), and add the minimum separation distances between the explosive hazard facility and all other explosive hazard facilities and public areas required for the solid propellants in accordance with section 420.65, treating the solid propellants as explosive division 1.1.

(c) A launch site operator shall determine the minimum separation distances between the explosive hazard facility and all other explosive hazard facilities and public areas required for the liquid propellants in accordance with section 420.67(b)(5), and add the minimum separation distances between the explosive hazard facility and all other explosive hazard facilities and public areas required for the solid propellants in accordance with section 420.65, using the explosive equivalent of the explosive division 1.3.

(d) A launch site operator shall conduct an analysis of the maximum credible event (MCE), or the worst case explosion that is expected to occur. If the MCE shows that there will be no simultaneous explosion reaction of the liquid propellant tanks and the solid propellant motors, then the minimum distance between the explosive hazard facility and all other explosive hazard facilities and public areas must be based on the MCE.

(a) Lightning protection. A licensee shall ensure that the public is not exposed to hazards due to the initiation of explosives by lightning.

(1) Elements of a lighting protection system. Unless an explosive hazard facility meets the conditions of paragraph (a)(3) of this section, all explosive hazard facilities shall have a lightning protection system to ensure explosives are not initiated by lightning. A lightning protection system shall meet the requirements of this paragraph and include the following:

(i) Air terminal. An air terminal to intentionally attract a lightning strike.

(ii) Down conductor. A low impedance path connecting an air terminal to an earth electrode system.

(iii) Earth electrode system. An earth electrode system to dissipate the current from a lightning strike to ground.

(2) Bonding and surge protection. A lightning protection system must meet the requirements of this paragraph and include the following:

(i) Bonding. All metallic bodies shall be bonded to ensure that voltage potentials due to lightning are equal everywhere in the explosive hazard facility. Any fence within six feet of a lightning protection system shall have a bond across each gate and other discontinuations and shall be bonded to the lightning protection system. Railroad tracks that run within six feet of the lightning protection system shall be bonded to the lightning protection system.

(ii) Surge protection. A lightning protection system shall include surge protection to reduce transient voltages due to lightning to a harmless level for all metallic power, communication, and instrumentation lines entering an explosive hazard facility.

(3) Circumstances where no lightening protection system is required. No lightning protection system is required for an explosive hazard facility when a lightning warning system is available to permit termination of operations and withdrawal of the public to public area distance prior to an electrical storm, or for an explosive hazard facility containing explosives that cannot be initiated by lightning. If no lightning protection system is required, a licensee must ensure the withdrawal of the public to a public area distance prior to an electrical storm.

(4) Testing and inspection. Lightning protection systems shall be visually inspected semiannually and shall be tested once each year for electrical continuity and adequacy of grounding. A licensee shall maintain at the explosive hazard facility a record of results obtained from the tests, including any action taken to correct deficiencies noted.

(b) Electrical power lines. A licensee shall ensure that electric power lines at its launch site meet the following requirements:

(1) Electric power lines shall be no closer to an explosive hazard facility than the length of the lines between the poles or towers that support the lines unless an effective means is provided to ensure that energized lines cannot, on breaking, come in contact with the explosive hazard facility.

(2) Towers or poles supporting electrical distribution lines that carry between 15 and 69 KV, and unmanned electrical substations shall be no closer to an explosive hazard facility than the public area distance for that explosive hazard facility.

(3) Towers or poles supporting electrical transmission lines that carry 69 KV or more, shall be no closer to an explosive hazard facility than the public area distance for that explosive hazard facility.

(a) Introduction

(1) This appendix provides a method for constructing a flight corridor from a launch point for a guided suborbital launch vehicle or any one of the four classes of guided orbital launch vehicles from table 1, §420.19, without the use of local meteorological data or a launch vehicle trajectory.

(2) A flight corridor includes an overflight exclusion zone in a launch area and, for a guided suborbital launch vehicle, an impact dispersion area in a downrange area. A flight corridor for a guided suborbital launch vehicle ends with the impact dispersion area, and, for the four classes of guided orbital launch vehicles, 5000 nautical miles (nm) from the launch point.

(b) Data requirements

(1) Maps. An applicant shall use any map for the launch site region with a scale not less than 1:250,000 inches per inch in the launch area and 1:20,000,000 inches per inch in the downrange area. As described in paragraph (b)(2), an applicant shall use a mechanical method, a semi-automated method, or a fully-automated method to plot a flight corridor on maps. A source for paper maps acceptable to the FAA is the U.S. Dept. of Commerce, National Oceanic and Atmospheric Administration, National Ocean Service.

(i) Projections for mechanical plotting method. An applicant shall use a conic projection. The FAA will accept a “Lambert-Conformal” conic projection. A polar aspect of a plane-azimuthal projection may also be used for far northern launch sites.

(ii) Projections for semi-automated plotting method. An applicant shall use cylindrical, conic, or plane projections for semi-automated plotting. The FAA will accept “Mercator” and “Oblique Mercator” cylindrical projections. The FAA will accept “Lambert-Conformal” and “Albers Equal-Area” conic projections. The FAA will accept “Lambert Azimuthal Equal-Area” and “Azimuthal Equidistant” plane projections.

(iii) Projections for fully-automated plotting method. The FAA will accept map projections used by geographical information system software scaleable pursuant to the requirements of paragraph (b)(1).

(2) Plotting Methods.

(i) Mechanical method. An applicant may use mechanical drafting equipment such as pencil, straight edge, ruler, protractor, and compass to plot the location of a flight corridor on a map. The FAA will accept straight lines for distances less than or equal to 7.5 times the map scale on map scales greater than or equal to 1:1,000,000 inches per inch (in/in); or straight lines representing 100 nm or less on map scales less than 1:1,000,000 in/in.

(ii) Semi-automated method. An applicant may employ the range and bearing techniques in paragraph (b)(3) to create latitude and longitude points on a map. The FAA will accept straight lines for distances less than or equal to 7.5 times the map scale on map scales greater than or equal to 1:1,000,000 inches per inch (in/in); or straight lines representing 100 nm or less on map scales less than 1:1,000,000 in/in.

(iii) Fully-automated method. An applicant may use geographical information system software with global mapping data scaleable in accordance with paragraph (b)(1).

(3) Range and bearing computations on an ellipsoidal Earth model.

(i) To create latitude and longitude pairs on an ellipsoidal Earth model, an applicant shall use the following equations to calculate geodetic latitude (+N) and longitude (+E) given the launch point geodetic latitude (+N), longitude (+E), range (nm), and bearing (degrees, positive clockwise from North).

(A) Input. An applicant shall use the following input in making range and bearing computations. Angle units must be in radians.

(B) Computations. An applicant shall use the following equations to determine the latitude (φ₂) and longitude (λ₂) of a target point situated “S” nm from the launch point on an azimuth bearing (α₁₂) degrees.

where:

a = WGS–84 semi-major axis (3443.91846652 nmi)

b = WGS–84 semi-minor axis (3432.37165994 nmi)

(ii) To create latitude and longitude pairs on an ellipsoidal Earth model, an applicant shall use the following equations to calculate the distance (S) of the geodesic between two points (P₁ and P₂), the forward azimuth (α₁₂) of the geodesic at P₁, and the back azimuth (α₂₁) of the geodesic at P₂, given the geodetic latitude (+N), longitude (+E) of P₁ and P₂. Azimuth is measured positively clockwise from North.

(A) Input. An applicant shall use the following input. Units must be in radians.

(B) Computations. An applicant shall use the following equations to determine the distance (S), the forward azimuth (α₁₂) of the geodesic at P₁, and the back azimuth (α₁₂) of the geodesic at P₂.

where:

a = WGS–84 semi-major axis (3443.91846652 nmi)

b = WGS–84 semi-minor axis (3432.37165994 nmi)

(c) Creation of a Flight Corridor

(1) To define a flight corridor, an applicant shall:

(i) Select a guided suborbital or orbital launch vehicle, and, for an orbital launch vehicle, select from table 1 of §420.19 a launch vehicle weight class that best represents the launch vehicle the applicant plans to support at its launch point;

(ii) Select a debris dispersion radius (D_max) from table A–1 corresponding to the guided suborbital launch vehicle or orbital launch vehicle class selected in paragraph (c)(1)(i);

(iii) Select a launch point geodetic latitude and longitude; and

(iv) Select a flight azimuth.

(2) An applicant shall define and map an overflight exclusion zone using the following method:

(i) Select a debris dispersion radius (D_max) from table A–1 and a downrange distance (D_OEZ) from table A–2 to define an overflight exclusion zone for the guided suborbital launch vehicle or orbital launch vehicle class selected in paragraph (c)(1)(i).

(ii) An overflight exclusion zone is described by the intersection of the following boundaries, which are depicted in figure A–1:

(A) An applicant shall define an uprange boundary with a half-circle arc of radius D_max and a chord of length twice D_max connecting the half-circle arc endpoints. The uprange boundary placement on a map has the chord midpoint positioned on the launch point with the chord oriented along an azimuth ±90°from the launch azimuth and the half-circle arc located uprange from the launch point.

(B) An applicant shall define the downrange boundary with a half-circle arc of radius D_max and a chord of length twice D_max connecting the half-circle arc endpoints. The downrange boundary placement on a map has the chord midpoint intersecting the nominal flight azimuth line at a distance D_OEZ inches downrange with the chord oriented along an azimuth ±90°from the launch azimuth and the half-circle arc located downrange from the intersection of the chord and the flight azimuth line.

(C) Crossrange boundaries of an overflight exclusion zone are defined by two lines segments. Each is parallel to the flight azimuth with one to the left side and one to the right side of the flight azimuth line. Each line connects an uprange half-circle arc endpoint to a downrange half-circle arc endpoint as shown in figure A–1.

(iii) An applicant shall identify the overflight exclusion zone on a map that meets the requirements of paragraph (b).

(3) An applicant shall define and map a flight corridor using the following method:

(i) In accordance with paragraph (b), an applicant shall draw a flight corridor on one or more maps with the D_max origin centered on the intended launch point and the flight corridor centerline (in the downrange direction) aligned with the initial flight azimuth. The flight corridor is depicted in figure A–2 and its line segment lengths are tabulated in table A–3.

(ii) An applicant shall define the flight corridor using the following boundary definitions:

(A) An applicant shall draw an uprange boundary, which is defined by an arc-line GB (figure A–2), directly uprange from and centered on the intended launch point with radius D_max.

(B) An applicant shall draw line CF perpendicular to and centered on the flight azimuth line, and positioned 10 nm downrange from the launch point. The applicant shall use the length of line CF provided in table A–3 corresponding to the guided suborbital launch vehicle or orbital launch vehicle class selected in paragraph (c)(1)(i).

(C) An applicant shall draw line DE perpendicular to and centered on the flight azimuth line, and positioned 100 nm downrange from the launch point. The applicant shall use the length of line DE provided in table A–3 corresponding to the guided suborbital launch vehicle or orbital launch vehicle class selected in paragraph (c)(1)(i).

(D) Except for a guided suborbital launch vehicle, an applicant shall draw a downrange boundary, which is defined by line HI and is drawn perpendicular to and centered on the flight azimuth line, and positioned 5,000 nm downrange from the launch point. The applicant shall use the length of line HI provided in table A–3 corresponding to the orbital launch vehicle class selected in paragraph (c)(1)(i).

(E) An applicant shall draw crossrange boundaries, which are defined by three lines on the left side and three lines on the right side of the flight azimuth. An applicant shall construct the left flight corridor boundary according to the following, and as depicted in figure A–3 :

(1) The first line (line BC in figure A–3) is tangent to the uprange boundary arc, and ends at endpoint C of line CF, as depicted in figure A–3;

(2) The second line (line CD in figure A–3) begins at endpoint C of line BC and ends at endpoint D of line DH, as depicted in figure A–3;

(3) For all orbital launch vehicles, the third line (line DH in figure A–3) begins at endpoint D of line CD and ends at endpoint H of line HI, as depicted in figure A–3; and

(4) For a guided suborbital launch vehicle, the line DH begins at endpoint D of line CD and ends at a point tangent to the impact dispersion area drawn in accordance with paragraph (c)(4) and as depicted in figure A–4.

(F) An applicant shall repeat the procedure in paragraph (c)(3)(ii)(E) for the right side boundary.

(iii) An applicant shall identify the flight corridor on a map that meets the requirements of paragraph (b).

(4) For a guided suborbital launch vehicle, an applicant shall define a final stage impact dispersion area as part of the flight corridor and show the impact dispersion area on a map, as depicted in figure A–4, in accordance with the following:

(i) An applicant shall select an apogee altitude (H_ap) for the launch vehicle final stage. The apogee altitude should equal the highest altitude intended to be reached by a guided suborbital launch vehicle launched from the launch point.

(ii) An applicant shall define the impact dispersion area by using an impact range factor [IP(H_ap)] and a dispersion factor [DISP(H_ap)] as shown below:

(A) An applicant shall calculate the impact range (D) for the final launch vehicle stage. An applicant shall set D equal to the maximum apogee altitude (H_ap) multiplied by the impact range factor as shown below:

where: IP(H_ap) = 0.4 for an apogee less than 100 km; and IP(H_ap) = 0.7 for an apogee 100 km or greater.

(B) An applicant shall calculate the impact dispersion radius (R) for the final launch vehicle stage. An applicant shall set R equal to the maximum apogee altitude (H_ap) multiplied by the dispersion factor as shown below:

where: DISP(H_ap) = 0.05

(iii) An applicant shall draw the impact dispersion area on a map with its center on the predicted impact point. An applicant shall then draw line DH in accordance with paragraph (c)(3)(ii)(E)(4).

(d) Evaluate the Flight Corridor

(1) An applicant shall evaluate the flight corridor for the presence of any populated areas. If an applicant determines that no populated area is located within the flight corridor, then no additional steps are necessary.

(2) If a populated area is located in an overflight exclusion zone, an applicant may modify its proposal or demonstrate that there are times when no people are present or that the applicant has an agreement in place to evacuate the public from the overflight exclusion zone during a launch.

(3) If a populated area is located within the flight corridor, an applicant may modify its proposal and create another flight corridor pursuant to appendix A, use appendix B to narrow the flight corridor, or complete a risk analysis in accordance with appendix C.

(a) Introduction

(1) This appendix provides a method to construct a flight corridor from a launch point for a guided suborbital launch vehicle or any one of the four weight classes of guided orbital launch vehicles from table 1, §420.19, using local meteorological data and a launch vehicle trajectory.

(2) A flight corridor is constructed in two sections—one section comprising a launch area and one section comprising a downrange area. The launch area of a flight corridor reflects the extent of launch vehicle debris impacts in the event of a launch vehicle failure and applying local meteorological conditions. The downrange area reflects the extent of launch vehicle debris impacts in the event of a launch vehicle failure and applying vehicle imparted velocity, malfunctions turns, and vehicle guidance and performance dispersions.

(3) A flight corridor includes an overflight exclusion zone in the launch area and, for a guided suborbital launch vehicle, an impact dispersion area in the downrange area. A flight corridor for a guided suborbital launch vehicle ends with an impact dispersion area and, for the four classes of guided orbital launch vehicles, 5,000 nautical miles (nm) from the launch point, or where the IIP leaves the surface of the Earth, whichever is shorter.

(b) Data Requirements

(1) Launch area data requirements. An applicant shall satisfy the following data requirements to perform the launch area analysis of this appendix. The data requirements are identified in table B–1 along with sources where data acceptable to the FAA may be obtained.

(i) An applicant must select meteorological data that meet the specifications in table B–1 for the proposed launch site.

(ii) For a guided orbital launch vehicle, an applicant shall obtain or create a launch vehicle nominal trajectory. An applicant may use trajectory data from a launch vehicle manufacturer or generate a trajectory using trajectory simulation software. Trajectory time intervals shall be no greater than one second. If an applicant uses a trajectory computed with commercially available software, the software must calculate the trajectory using the following parameters, or clearly and convincingly demonstrated equivalents:

(A) Launch location:

(1) Launch point, using geodetic latitude and longitude to four decimal places; and

(2) Launch point height above sea level.

(B) Ellipsoidal Earth:

(1) Mass of Earth;

(2) Radius of Earth;

(3) Earth flattening factor; and

(4) Gravitational harmonic constants (J2, J3, J4).

(C) Vehicle characteristics:

(1) Mass as a function of time;

(2) Thrust as a function of time;

(3) Specific impulse (I_SP) as a function of time; and

(4) Stage dimensions.

(D) Launch events:

(1) Stage burn times; and

(2) Stage drop-off times.

(E) Atmosphere:

(1) Density as a function of altitude;

(2) Pressure as a function of altitude;

(3) Speed of sound as a function of altitude; and

(4) Temperature as a function of altitude.

(F) Winds:

(1) Wind direction as a function of altitude; and

(2) Wind magnitude as a function of altitude.

(I) Aerodynamics: drag coefficient as a function of mach number for each stage of flight showing subsonic, transonic and supersonic mach regions for each stage.

(iii) An applicant shall use a ballistic coefficient (β) of 3 lbs/ft² for debris impact computations.

(iv) An applicant shall satisfy the map and plotting requirements for a launch area of appendix A, paragraph (b).

(2) Downrange area data requirements. An applicant shall satisfy the following data requirements to perform the downrange area analysis of this appendix.

(i) The launch vehicle weight class and method of generating a trajectory used in the launch area shall be used by an applicant in the downrange area as well. Trajectory time intervals must not be greater than one second.

(ii) An applicant shall satisfy the map and plotting data requirements for a downrange area of appendix A, paragraph (b).

(c) Construction of a Launch Area of a Flight Corridor

(1) An applicant shall construct a launch area of a flight corridor using the processes and equations of this paragraph for each trajectory position. An applicant shall repeat these processes at time points on the launch vehicle trajectory for time intervals of no greater than one second. When choosing wind data, an applicant shall use a time period of between one and 12 months.

(2) A launch area analysis must include all trajectory positions whose Z-values are less than or equal to 50,000 ft.

(3) Each trajectory time is denoted by the subscript “i”. Height intervals for a given atmospheric pressure level are denoted by the subscript “j'.

(4) Using data from the GGUAS CD-ROM, an applicant shall estimate the mean atmospheric density, maximum wind speed, height interval fall times and height interval debris dispersions for 15 mean geometric height intervals.

(i) The height intervals in the GGUAS source data vary as a function of the following 15 atmospheric pressure levels expressed in millibars: surface, 1000, 850, 700, 500, 400, 300, 250, 200, 150, 100, 70, 50, 30, 10. The actual geometric height associated with each pressure level varies depending on the time of year. An applicant shall estimate the mean geometric height over the period of months selected in subparagraph (1) of this paragraph for each of the 15 pressure levels as shown in equation B1.

where:

H _j = mean geometric height h_m = geometric height for a given month n_m = number of observations for a given month

k = number of wind months of interest

(ii) The atmospheric densities in the source data also vary as a function of the 15 atmospheric pressure levels. The actual atmospheric density associated with each pressure level varies depending on the time of year. An applicant shall estimate the mean atmospheric density over the period of months selected in accordance with subparagraph (1) of this paragraph for each of the 15 pressure levels as shown in equation B2.

where:

ρ_j = mean atmospheric density

_

ρ_m = atmospheric density for a given month

n_m = number of observations for a given month

k = number of wind months of interest

(iii) An applicant shall estimate the algebraic maximum wind speed at a given pressure level as follows and shall repeat the process for each pressure level.

(A) For each month, an applicant shall calculate the monthly mean wind speed (W_az) for 360 azimuths using equation B3;

(B) An applicant shall select the maximum monthly mean wind speed from the 360 azimuths;

(C) An applicant shall repeat subparagraphs (c)(4)(iii)(A) and (B) for each month of interest; and

(D) An applicant shall select the maximum mean wind speed from the range of months. The absolute value of this wind is designated W_max for the current pressure level.

(iv) An applicant shall calculate wind speed using the means for winds from the West (u) and winds from the North (v). An applicant shall use equation B3 to resolve the winds to a specific azimuth bearing.

where:

az = wind azimuth

u = West zonal wind component

v = North zonal wind component

W_az = mean wind speed at azimuth for each month

(v) An applicant shall estimate the interval fall time over a height interval assuming the initial descent velocity is equal to the terminal velocity (V_T). An applicant shall use equations B4 through B6 to estimate the fall time over a given height interval.

where:

ΔH_Tj= height difference between two mean geometric heights

β= ballistic coefficient

_

ρx= mean atmospheric density for the corresponding mean geometric heights

V_Tj = terminal velocity

(vi) An applicant shall estimate the interval debris dispersion (D_j) by multiplying the interval fall time by the algebraic maximum mean wind speed (W_max) as shown in equation B7.

(5) Once the Dj are estimated for each height interval, an applicant shall determine the total debris dispersion (D_i) for each Z_i using a linear interpolation and summation exercise, as shown below in equation B8. An applicant shall use a launch point height of zero equal to the surface level of the nearest GGUAS grid location.

where:

n = number of height intervals below jth height interval

(6) Once all the D_i radii have been calculated, an applicant shall produce a launch area flight corridor in accordance with the requirements of subparagraphs (c)(6)(i)–(iv).

(i) On a map meeting the requirements of appendix A, paragraph (b), an applicant shall plot the X_i position location on the flight azimuth for the corresponding Z_i position;

(ii) An applicant shall draw a circle of radius D_i centered on the corresponding X_i position; and

(iii) An applicant shall repeat the instructions in subparagraphs (c)(6)(i)–(ii) for each D_i radius.

(iv) The launch area of a flight corridor is the enveloping line that encloses the outer boundary of the D_i circles as shown in Fig. B–1. The uprange portion of a flight corridor is described by a semi-circle arc that is a portion of either the most uprange D_i dispersion circle, or the overflight exclusion zone (defined by subparagraph (c)(7)), whichever is further uprange.

(7) An applicant shall define an overflight exclusion zone in the launch area in accordance with the requirements of appendix A, subparagraph (c)(2).

(8) An applicant shall draw the launch area flight corridor and overflight exclusion zone on a map or maps that meet the requirements of table B–1.

(d) Construction of a Downrange Area of a Flight Corridor

(1) The downrange area analysis estimates the debris dispersion for the downrange time points on a launch vehicle trajectory. An applicant shall perform the downrange area analysis using the processes and equations of this paragraph.

(2) The downrange area analysis shall include trajectory positions at a height (the Z_i-values) greater than 50,000 feet and nominal trajectory IIP values less than or equal to 5,000 nm. For a guided suborbital launch vehicle, the final IIP value for which an applicant must account is the launch vehicle final stage impact point. Each trajectory time shall be one second or less and is denoted by the subscript “i'.

(3) An applicant shall compute the downrange area of a flight corridor boundary in four steps, from each trajectory time increment: determine a reduction ratio factor; calculate the launch vehicle position after simulating a malfunction turn; rotate the state vector after the malfunction turn in the range of three degrees to one degree as a function of X_i distance downrange; and compute the IIP of the resulting trajectory. The locus of IIPs describes the boundary of the downrange area of a flight corridor. An applicant shall use the following subparagraphs, (d)(3)(i)–(v), to compute the downrange area of the flight corridor boundary:

(i) Compute the downrange Distance to the final IIP position for a nominal trajectory as follows:

(A) Using equations B30 through B69, determine the IIP coordinates (φ_max, λ_max) for the nominal state vector before the launch vehicle enters orbit where α in equation B30 is the nominal flight azimuth angle measured from True North.

(B) Using the range and bearing equations of appendix A, paragraph (b)(3), determine the distance (S_max) from the launch point coordinates (φ_lp, λ_lp) to the IIP coordinates (φ_max, λ_max) computed in accordance with (3)(i)(A) of this paragraph.

(C) The distance for S_max may not exceed 5000 nm. In cases when the actual value exceeds 5000 nm the applicant shall use 5000 nm for S_max.

(ii) Compute the reduction ratio factor (F_n) for each trajectory time increment as follows:

(A) Using equations B30 through B69, determine the IIP coordinates (φ_i, λ_i) for the nominal state vector where α in equation B30 is the nominal flight azimuth angle measured from True North.

(B) Using the range and bearing equations of appendix A, paragraph (b)(3), determine the distance (S_i) from the launch point coordinates (φ_lp, λ_lp) to the IIP coordinates (φ_i, λ_i) computed in (3)(ii)(A) of this paragraph.

(C) The reduction ratio factor is:

(iii) An applicant shall compute the launch vehicle position and velocity components after a simulated malfunction turn for each X_i using the following method.

(A) Turn duration (Δt) = 4 sec.

(B) Turn angle (Θ)

The turn angle equations perform a turn in the launch vehicle's yaw plane, as depicted in figure B–2.

(C) Launch vehicle velocity magnitude at the beginning of the turn (V_b) and velocity magnitude at the end of the turn (V_e)

(D) Average velocity magnitude over the turn duration (V )

(E) Velocity vector path angle (γ_i) at turn epoch

(F) Launch vehicle position components at the end of turn duration

where: g₁ = 32.17405 ft/sec²

(G) Launch vehicle velocity components at the end of turn duration

(iv) An applicant shall rotate the trajectory state vector at the end of the turn duration to the right and left to define the right-lateral flight corridor boundary and the left-lateral flight corridor boundary, respectively. An applicant shall perform the trajectory rotation in conjunction with a trajectory transformation from the X₉₀, Y₉₀, Z₉₀, X ₉₀, Y ₉₀, Z ₉₀, components to E, N, U, E , N , U . The trajectory subscripts “R” and “L” from equations B15 through B26 have been discarded to reduce the number of equations. An applicant shall transform from to E,N,U,E ,N ,U to E,F,G,E ,F ,G . An applicant shall use the equations of paragraph (d)(3)(iv)(A)–(F) to produce the EFG components necessary to estimate each instantaneous impact point.

(A) An applicant must calculate the flight angle (α)

(B) An applicant shall transform X₉₀,Y₉₀,Z₉₀ to E,N,U

(C) An applicant shall transform to X ₉₀, Y ₉₀, Z ₉₀ to E , N , U .

(D) An applicant shall transform the launch point coordinates (φ₀λ₀,h₀) to E₀,F₀,G₀

(E) An applicant shall transform E,N,U to E₉₀,F₉₀,G₉₀

(F) An applicant shall transform to E ,N ,U TO E ,F ,G

(v) The IIP computation implements an iterative solution to the impact point problem. An applicant shall solve equations B46 through B69, with the appropriate substitutions, up to a maximum of five times. Each repetition of the equations provides a more accurate prediction of the IIP. An applicant shall use the required IIP computations of paragraphs (d)(3)(v)(A)–(W) below. An applicant shall use this IIP computation for both the left-and right-lateral offsets. The IIP computations will result in latitude and longitude pairs for the left-lateral flight corridor boundary and the right-lateral flight corridor boundary. An applicant shall use the lines connecting the latitude and longitude pairs to describe the entire downrange area boundary of the flight corridor up to 5000 nm or a final stage impact dispersion area.

(A) An applicant shall approximate the radial distance (r_k,l) from the geocenter to the IIP. The distance from the center of the Earth ellipsoid to the launch point shall be used for the initial approximation of r_k,l as shown in equation B46.

(B) An applicant shall compute the radial distance (r) from the geocenter to the launch vehicle position.

If r < r_k,l then the launch vehicle position is below the Earth's surface and an impact point cannot be computed. An applicant must restart the calculations with the next trajectory state vector.

(C) An applicant shall compute the inertial velocity components.

where: ω = 4.178074×10⁻³ deg/sec

(D) An applicant shall compute the magnitude of the inertial velocity vector.

(E) An applicant shall compute the eccentricity of the trajectory ellipse multiplied by the cosine of the eccentric anomaly at epoch ε_c).

where: K = 1.407644×10¹⁶ ft³ /sec²

(F) An applicant shall compute the semi-major axis of the trajectory ellipse (a^t ).

If at 0 or at then the trajectory orbit is not elliptical, but is hyperbolic or parabolic, and an impact point cannot be computed. The launch vehicle has achieved escape velocity and the applicant may terminate computations.

(G) An applicant shall compute the eccentricity of the trajectory ellipse multiplied by the sine of the eccentric anomaly at epoch ε_s).

(H) An applicant shall compute the eccentricity of the trajectory ellipse squared ε² ).

If a_t(1−ε)−a_E] > 0 and ε ≥ 0 then the trajectory perigee height is positive and an impact point cannot be computed. The launch vehicle has achieved Earth orbit and the applicant may terminate computations.

(I) An applicant shall compute the eccentricity of the trajectory ellipse multiplied by the cosine of the eccentric anomaly at impact (ε_ck).

(J) An applicant shall compute the eccentricity of the trajectory ellipse multiplied by the sine of the eccentric anomaly at impact (ε_sk).

If ε_sk < 0 then the trajectory orbit does not intersect the Earth's surface and an impact point cannot be computed. The launch vehicle has achieved Earth orbit and the applicant may terminate computations.

(K) An applicant shall compute the cosine of the difference between the eccentric anomaly at impact and the eccentric anomaly at epoch (Δε_ck).

(L) An applicant shall compute the sine of the difference between the eccentric anomaly at impact and the eccentric anomaly at epoch (Δε_sk).

(M) An applicant shall compute the f-series expansion of Kepler's equations.

(N) An applicant shall compute the g-series expansion of Kepler's equations.

(O) An applicant shall compute the E,F,G coordinates at impact (E_i,F_i,G_i).

(P) An applicant shall approximate the distance from the geocenter to the launch vehicle position at impact (r_k,2).

where:

a_E = 20925646.3255 ft

e² = 0.00669437999013

(Q) An applicant shall let rk+1,1 = r_k,2, substitute rk+1,1 for r_k,1 in equation B55 and repeat equations B55—B64 up to four more times increasing “k” by an increment of one on each loop (e.g. kε{1, 2, 3, 4, 5}). If |r_5,1−r_5,2| > 1 then the iterative solution does not converge and an impact point does not meet the accuracy tolerance of plus or minus one foot. An applicant must try more iterations, or restart the calculations with the next trajectory state vector.

(R) An applicant shall compute the difference between the eccentric anomaly at impact and the eccentric anomaly at epoch (Δε).

(S) An applicant shall compute the time of flight from epoch to impact (t).

(T) An applicant shall compute the geocentric latitude at impact (φ').

Where: +90°>φ′_i> −90°

(U) An applicant shall compute the geodetic latitude at impact (φ).

Where: +90°>φ_i> −90°

(V) An applicant shall compute the East longitude at impact (λ).

(W) If the range from the launch point to the impact point is equal to or greater than 5000 nm, an applicant shall terminate IIP computations.

(4) For a guided suborbital launch vehicle, an applicant shall define a final stage impact dispersion area as part of the flight corridor and show the area on a map using the following procedure:

(i) For equation B70 below, an applicant shall use an apogee altitude (H_ap) corresponding to the highest altitude reached by the launch vehicle final stage in the applicant's launch vehicle trajectory analysis done in accordance with paragraph (b)(1)(ii).

(ii) An applicant shall define the final stage impact dispersion area by using a dispersion factor [DISP(H_ap)] as shown below. An applicant shall calculate the impact dispersion radius (R) for the final launch vehicle stage. An applicant shall set R equal to the maximum apogee altitude (H_ap) multiplied by the dispersion factor as shown below:

where: DISP(H_ap) = 0.05

(5) An applicant shall combine the launch area and downrange area flight corridor and any final stage impact dispersion area for a guided suborbital launch vehicle.

(i) On the same map with the launch area flight corridor, an applicant shall plot the latitude and longitude positions of the left and right sides of the downrange area of the flight corridor calculated in accordance with subparagraph (d)(3).

(ii) An applicant shall connect the latitude and longitude positions of the left side of the downrange area of the flight corridor sequentially starting with the last IIP calculated on the left side and ending with the first IIP calculated on the left side. An applicant shall repeat this procedure for the right side.

(iii) An applicant shall connect the left sides of the launch area and downrange portions of the flight corridor. An applicant shall repeat this procedure for the right side.

(iv) An applicant shall plot the overflight exclusion zone defined in subparagraph (c)(7).

(v) An applicant shall draw any impact dispersion area on the downrange map with the center of the impact dispersion area on the launch vehicle final stage impact point obtained from the applicant's launch vehicle trajectory analysis done in accordance with subparagraph (b)(1)(ii).

(e) Evaluate the Launch Site

(1) An applicant shall evaluate the flight corridor for the presence of populated areas. If no populated area is located within the flight corridor, then no additional steps are necessary.

(2) If a populated area is located in an overflight exclusion zone, an applicant may modify its proposal or demonstrate that there are times when no people are present or that the applicant has an agreement in place to evacuate the public from the overflight exclusion zone during a launch.

(3) If a populated area is located within the flight corridor, an applicant may modify its proposal or complete an overflight risk analysis in accordance with appendix C.

(a) Introduction

(1) This appendix provides a method for an applicant to estimate the expected casualty (E_c) for a launch of a guided expendable launch vehicle using a flight corridor generated either by appendix A or appendix B. This appendix also provides an applicant options to simplify the method where population at risk is minimal.

(2) An applicant shall perform a risk analysis when a populated area is located within a flight corridor defined by either appendix A or appendix B. If the estimated expected casualty exceeds 30×10⁻⁶, an applicant may either modify its proposal, or if the flight corridor used was generated by the appendix A method, use the appendix B method to narrow the flight corridor and then redo the overflight risk analysis pursuant to this appendix. If the estimated expected casualty still exceeds 30×10⁻⁶ the FAA will not approve the location of the proposed launch point.

(b) Data Requirements

(1) An applicant shall obtain the data specified by subparagraphs (b)(2) and (3) and summarized in table C–1. Table C–1 provides sources where an applicant may obtain data acceptable to the FAA. An applicant must also employ the flight corridor information from appendix A or B, including flight azimuth and, for an appendix B flight corridor, trajectory information.

(2) Population data. Total population (N) and the total landmass area within a populated area (A) are required. Population data up to and including 100 nm from the launch point are required at the U.S. census block group level. Population data downrange from 100 nm are required at no greater than 1° × 1° latitude/longitude grid coordinates.

(3) Launch vehicle data. Launch vehicle data consist of the launch vehicle failure probability (P_f), the launch vehicle effective casualty area (A_c), trajectory position data, and the overflight dwell time (t_d). The failure probability is a constant (P_f = 0.10) for a guided orbital or suborbital expendable launch vehicle. Table C–3 provides effective casualty area data based on IIP range. Trajectory position information is provided from distance computations provided by this appendix for an appendix A flight corridor, or trajectory data used in appendix B for an appendix B flight corridor. The dwell time (t_d) may be determined from trajectory data produced when creating an appendix B flight corridor.

(c) Estimating Corridor Casualty Expectation

(1) A corridor casualty expectation [E_C(Corridor)] estimate is the sum of the expected casualty measurement of each populated area inside a flight corridor.

(2) An applicant shall identify and locate each populated area in the proposed flight corridor.

(3) An applicant shall determine the probability of impact in each populated area using the procedures in subparagraphs (5) or (6) of this paragraph. Figures C–1 and C–2 illustrate an area considered for probability of impact (P_i ) computations by the dashed-lined box around the populated area within a flight corridor, and figure C–3 illustrates a populated area in a final stage impact dispersion area. An applicant shall then estimate the E_C for each populated area in accordance with subparagraphs (7) and (8) of this paragraph.

(4) The P_i computations do not directly account for populated areas whose areas are bisected by an appendix A flight corridor centerline or an appendix B nominal trajectory ground trace. Accordingly, an applicant must evaluate P_i for each of the bi-sections as two separate populated areas, as shown in figure C–4, which shows one bi-section to the left of an appendix A flight corridor's centerline and one to its right.

(5) Probability of impact (P_i) computations for a populated area in an appendix A flight corridor. An applicant shall compute P_i for each populated area using the following method:

(i) For the launch and downrange areas, but not for a final stage impact dispersion area for a guided suborbital launch vehicle, an applicant shall compute P_i for each populated area using the following equation:

where:

x₁, x₂ = closest and farthest downrange distance (nm) along the flight corridor centerline to the populated area (see figure C–1)

y₁, y₂ = closest and farthest cross range distance (nm) to the populated area measured from the flight corridor centerline (see figure C–1)

σ_y = one-third of the cross range distance from the centerline to the flight corridor boundary (see figure C–1)

exp = exponential function (e^x )

P_f = probability of failure = 0.10

R = IIP range rate (nm/sec) (see table C–2)

C = 643 seconds (constant)

(ii) For each populated area within a final stage impact dispersion area, an applicant shall compute P_i using the following method:

(A) An applicant shall estimate the probability of final stage impact in the x and y sectors of each populated area within the final stage impact dispersion area using equations C2 and C3:

where:

X₁, X₂ = closest and farthest downrange distance, measured along the flight corridor centerline, measured from the nominal impact point to the populated area (see figure C–3)

σ_x = one-third of the impact dispersion radius (see figure C–3)

exp = exponential function (e^x )

where:

y₁, y₂ = closest and farthest cross range distance to the populated area measured from the flight corridor centerline (see figure C–3)

σ_y = one-third of the impact dispersion radius (see figure C–3)

exp = exponential function (e^x )

(B) If a populated area intersects the impact dispersion area boundary so that the x₂ or y₂ distance would otherwise extend outside the impact dispersion area, the x₂ or y₂ distance should be set equal to the impact dispersion area radius. The x₂ distance for populated area A in figure C–3 is an example. If a populated area intersects the flight azimuth, an applicant shall solve equation C3 by obtaining the solution in two parts. An applicant shall determine, first, the probability between y₁ = 0 and y₂ = a and, second, the probability between y₁ = 0 and y₂ = b, as depicted in figure C–4. The probability P_y is then equal to the sum of the probabilities of the two parts. If a populated area intersects the line that is normal to the flight azimuth on the impact point, an applicant shall solve equation C2 by obtaining the solution in two parts in the same manner as with the values of x.

(C) An applicant shall calculate the probability of impact for each populated area using equation C4 below:

where: P_s = 1−P_f = 0.90

(6) Probability of impact computations for a populated area in an appendix B flight corridor. An applicant shall compute P_i using the following method:

(i) For the launch and downrange areas, but not for a final stage impact dispersion area for a guided suborbital launch vehicle, an applicant shall compute P_i for each populated area using the following equation:

where:

y₁,y₂ = closest and farthest cross range distance (nm) to a populated area measured from the nominal trajectory IIP ground trace (see figure C–2)

σ_y = one-third of the cross range distance (nm) from nominal trajectory to the flight corridor boundary (see figure C–2)

exp = exponential function (e^x )

P_f = probability of failure = 0.10

t = flight time from lift-off to orbital insertion (seconds)

t_d = overflight dwell time (seconds)

(ii) For each populated area within a final stage impact dispersion area, an applicant shall compute P_i using the following method:

(A) An applicant shall estimate the probability of final stage impact in the x and y sectors of each populated area within the final stage impact dispersion area using equations C6 and C7:

where:

x₁, x₂ = closest and farthest downrange distance, measured along nominal trajectory IIP ground trace, measured from the nominal impact point to the populated area (see figure C–3)

σ_x = one-third of the impact dispersion radius (see figure C–3)

exp = exponential function (e^x )

where:

y₁, y₂ = closest and farthest cross range distance to the populated area measured from the nominal trajectory IIP ground trace (see figure C–3)

σ_y = one-third of the impact dispersion radius (see figure C–3)

exp = exponential function (e^x )

(B) If a populated area intersects the impact dispersion area boundary so that the x₂ or y₂ distance would otherwise extend outside the impact dispersion area, the x₂ or y₂ distance should be set equal to the impact dispersion area radius. The x₂ distance for populated area A in figure C–3 is an example. If a populated area intersects the flight azimuth, an applicant shall solve equation C7 by obtaining the solution in two parts. An applicant shall determine, first, the probability between y₁ = 0 and y₂ = a and, second, the probability between y₁ = 0 and y₂ = b, as depicted in figure C–4. The probability P_y is then equal to the sum of the probabilities of the two parts. If a populated area intersects the line that is normal to the flight azimuth on the impact point, an applicant shall solve equation C6 by obtaining the solution in two parts in a similar manner with the values of x.

(C) An applicant shall calculate the probability of impact for each populated area using equation C8 below:

where: P_s = 1−P_f = 0.90

(7) Using the P_i calculated in either subparagraph (c)(5) or (6) of this paragraph, an applicant shall calculate the casualty expectancy for each populated area within the flight corridor in accordance with equation C9. E_ck is the casualty expectancy for a given populated area as shown in equation C9, where individual populated areas are designated with the subscript “k”.

where:

A_c = casualty area (from table C–3)

A_k = populated area

N_k = population in A_k

(8) An applicant shall estimate the total corridor risk using the following summation of risk:

(9) Alternative casualty expectancy (E_C ) analyses. An applicant may employ specified variations to the analysis defined by subparagraphs (c)(1)–(8). Those variations are identified in subparagraphs (9)(i) through (vi) of this paragraph. Subparagraphs (i) through (iv) permit an applicant to make conservative assumptions that would lead to an overestimation of the corridor E_C compared with the analysis defined by subparagraphs (c)(1)–(8). In subparagraphs (v) and (vi), an applicant that would otherwise fail the analysis prescribed by subparagraphs (c)(1)–(8) may avoid (c)(1)–(8)'s overestimation of the probability of impact in each populated area. An applicant employing a variation shall identify the variation used, show and discuss the specific assumptions made to modify the analysis defined by subparagraphs (c)(1)–(8), and demonstrate how each assumption leads to overestimation of the corridor E_C compared with the analysis defined by subparagraphs (c)(1)–(c)(8).

(i) Assume that P_x and P_y have a value of 1.0 for all populated areas.

(ii) Combine populated areas into one or more larger populated areas, and use a population density for the combined area or areas equal to the most densely populated area.

(iii) For any given populated area, assume P_y has a value of one.

(iv) For any given P_x sector (an area spanning the width of a flight corridor and bounded by two time points on the trajectory IIP ground trace) assume P_y has a value of one and use a population density for the sector equal to the most densely populated area.

(v) For a given populated area, divide the populated area into smaller rectangles, determine P_i for each individual rectangle, and sum the individual impact probabilities to determine P_i for the entire populated area.

(vi) For a given populated area, use the ratio of the populated area to the area of the P_i rectangle from the subparagraph (c)(1)–(8) analysis.

(d) Evaluation of Results

(1) If the estimated expected casualty does not exceed 30×10⁻⁶, the FAA will approve the launch site location.

(2) If the estimated expected casualty exceeds 30×10⁻⁶, then an applicant may either modify its proposal, or, if the flight corridor used was generated by the appendix A method, use the appendix B method to narrow the flight corridor and then perform another appendix C risk analysis.

(a) Introduction

(1) This appendix provides a method for determining the acceptability of the location of a launch point from which an unguided suborbital launch vehicle would be launched. The appendix describes how to define an overflight exclusion zone and impact dispersion areas, and how to evaluate whether the public risk presented by the launch of an unguided suborbital launch vehicle remains at acceptable levels.

(2) An applicant shall base its analysis on an unguided suborbital launch vehicle whose final launch vehicle stage apogee represents the intended use of the launch point.

(3) An applicant shall use the apogee of each stage of an existing unguided suborbital launch vehicle with a final launch vehicle stage apogee equal to the one proposed, and calculate each impact range and dispersion area using the equations provided.

(4) This appendix also provides a method for performing an impact risk analysis that estimates the expected casualty (E_c) within each impact dispersion area. This appendix provides an applicant options to simplify the method where population at risk is minimal.

(5) If the estimated E_c is less than or equal to 30×10^−6, the FAA will approve the launch point for unguided suborbital launch vehicles. If the estimated E_c exceeds 30×10^−6, the proposed launch point will fail the launch site location review.

(b) Data Requirements

(1) An applicant shall employ the apogee of each stage of an existing unguided suborbital launch vehicle whose final stage apogee represents the maximum altitude to be reached by unguided suborbital launch vehicles launched from the launch point. The apogee shall be obtained from one or more actual flights of an unguided suborbital launch vehicle launched at an 84 degree elevation.

(2) An applicant shall satisfy the map and plotting data requirements of appendix A, paragraph (b).

(3) Population data. An applicant shall use total population (N) and the total landmass area within a populated area (A) for all populated areas within an impact dispersion area. Population data up to and including 100 nm from the launch point are required at the U.S. census block group level. Population data downrange from 100 nm are required at no greater than 1° × 1° latitude/longitude grid coordinates.

(c) Overflight Exclusion Zone and Impact Dispersion Areas

(1) An applicant shall choose a flight azimuth from a launch point.

(2) An applicant shall define an overflight exclusion zone as a circle with a radius of 1600 feet centered on the launch point.

(3) An applicant shall define an impact dispersion area for each stage of the suborbital launch vehicle chosen in accordance with subparagraph (b)(1) in accordance with the following:

(i) An applicant shall calculate the impact range for the final launch vehicle stage (D_n). An applicant shall set D_n equal to the last stage apogee altitude (H_n) multiplied by an impact range factor [IP(H_n)] in accordance with the following:

where:

IP(H_n) = 0.4 for an apogee less than 100 km, and

IP(H_n) = 0.7 for an apogee of 100 km or greater.

(ii) An applicant shall calculate the impact range for each intermediate stage (D_i), where i ε {1, 2, 3, . . . (n− 1)}, and where n is the total number of launch vehicle stages. Using the apogee altitude (H_i) of each intermediate stage, an applicant shall use equation D1 to compute the impact range of each stage by substituting H_i for H_n. An applicant shall use the impact range factors provided by equation D1.

(iii) An applicant shall calculate the impact dispersion radius for the final launch vehicle stage (R_n). An applicant shall set R_n equal to the last stage apogee altitude (H_n) multiplied by an impact dispersion factor [DISP(H_n)] in accordance with the following:

where:

DISP(H_n) = 0.4 for an apogee less than 100 km, and

DISP(Hn) = 0.7 for an apogee of 100 km or greater.

(iv) An applicant shall calculate the impact dispersion radius for each intermediate stage (R_i), where i ε {1, 2, 3, . . . (n− 1)} and where n is the total number of launch vehicle stages. Using the apogee altitude (H_i) of each intermediate stage, an applicant shall use equation D2 to compute an impact dispersion radius of each stage by substituting H_i for H_n. An applicant shall use the dispersion factors provided by equation D2.

(4) An applicant shall display an overflight exclusion zone, each intermediate and final stage impact point (D_i through D_n), and each impact dispersion area for the intermediate and final launch vehicle stages on maps in accordance with paragraph (b)(2).

(d) Evaluate the Overflight Exclusion Zone and Impact Dispersion Areas

(1) An applicant shall evaluate the overflight exclusion zone and each impact dispersion area for the presence of any populated areas. If an applicant determines that no populated area is located within the overflight exclusion zone or any impact dispersion area, then no additional steps are necessary.

(2) If a populated area is located in an overflight exclusion zone, an applicant may modify its proposal or demonstrate that there are times when no people are present or that the applicant has an agreement in place to evacuate the public from the overflight exclusion zone during a launch.

(3) If a populated area is located within any impact dispersion area, an applicant may modify its proposal and define a new overflight exclusion zone and new impact dispersion areas, or perform an impact risk analysis in accordance with paragraph (e).

(e) Impact Risk Analysis

(1) An applicant shall estimate the expected average number of casualties, E_C, within the impact dispersion areas according to the following method:

(i) An applicant shall calculate the E_c by summing the impact risk for the impact dispersion areas of the final launch vehicle stage and all intermediate stages. An applicant shall estimate E_c for the impact dispersion area of each stage by using equations D3 through D7 for each of the populated areas located within the impact dispersion areas.

(ii) An applicant shall estimate the probability of impacting inside the X and Y sectors of each populated area within each impact dispersion area using equations D3 and D4:

where:

x₁, x₂ = closest and farthest downrange distance to populated area (see figure D–2)

σ_x = one-third of the impact dispersion radius (see figure D–2)

exp = exponential function (e^x )

where:

y₁, y₂ = closest and farthest cross range distance to the populated area (see figure D–2)

σ_y = one-third of the impact dispersion radius (see figure D–2)

exp = exponential function (e^x )

(iii) If a populated area intersects the impact dispersion area boundary so that the x₂ or y₂ distance would otherwise extend outside the impact dispersion area, the x₂ or y₂ distance should be set equal to the impact dispersion area radius. The x₂ distance for populated area A in figure D–2 is an example.

(iv) If a populated area intersects the flight azimuth, an applicant shall solve equation D4 by obtaining the solution in two parts. An applicant shall determine, first, the probability between y₁ = 0 and y₂ = a and, second, the probability between y₁ = 0 and y₂ = b, as depicted in figure D–3. The probability P_y is then equal to the sum of the probabilities of the two parts. If a populated area intersects the line that is normal to the flight azimuth on the impact point, an applicant shall solve equation D3 by obtaining the solution in two parts in the same manner as with the values of x.

(v) An applicant shall calculate the probability of impact (P_i) for each populated area using the following equation:

where:

P_s = probability of success = 0.98

(vi) An applicant shall calculate the casualty expectancy for each populated area. E_ck is the casualty expectancy for a given populated area as shown in equation D6, where individual populated areas are designated with the subscript “k”.

where:

k { {1, 2, 3, . . . , n}

A_c = casualty area (from table D–1)

A_k = populated area

N_k = population in A_k

(vii) An applicant shall estimate the total risk using the following summation of risk:

(viii) Alternative casualty expectancy (E_c) analysis. An applicant may employ specified variations to the analysis defined by subparagraphs (d)(1)(i)–(vii). Those variations are identified in subparagraphs (viii)(A) through (F) of this paragraph. Subparagraphs (A) through (D) permit an applicant to make conservative assumptions that would lead to an overestimation of E_c compared with the analysis defined by subparagraphs (d)(1)(i)–(vii). In subparagraphs (E) and (F), an applicant that would otherwise fail the analysis prescribed by subparagraphs (d)(1)(i)–(vii) may avoid (d)(1)(i)–(vii)'s overestimation of the probability of impact in each populated area. An applicant employing a variation shall identify the variation used, show and discuss the specific assumptions made to modify the analysis defined by subparagraphs (d)(1)(i)–(vii), and demonstrate how each assumption leads to overestimation of the corridor E_c compared with the analysis defined by subparagraphs (d)(1)(i)–(vii).

(A) Assume that P_x and P_y have a value of 1.0 for all populated areas.

(B) Combine populated areas into one or more larger populated areas, and use a population density for the combined area or areas equal to the most densely populated area.

(C) For any given populated area, assume P_x has a value of one.

(D) For any given populated area, assume P_y has a value of one.

(E) For a given populated area, divide the populated area into smaller rectangles, determine P_i for each individual rectangle, and sum the individual impact probabilities to determine P_i for the entire populated area.

(F) For a given populated area, use the ratio of the populated area to the area of the P_i rectangle used in the subparagraph (d)(1)(i)–(vii) analysis.

(2) If the estimated expected casualty does not exceed 30 × 10⁻⁶, the FAA will approve the launch point.

(3) If the estimated expected casualty exceeds 30 × 10⁻⁶, then an applicant may modify its proposal and then repeat the impact risk analysis in accordance with this appendix D. If no set of impact dispersion areas exist which satisfy the FAA's risk threshold, the applicant's proposed launch site will fail the launch site location review.