← Back to Files & Wiki
Wiki page · event · source_mapped

WAR.GOV D48 Air Force Report 1996

This page maps the D48 Air Force report lane inside WAR.GOV / PURSUE Release 01. It represents DOW UAP D48, Department of the Air Force Report, 1996 as an official technical source on launch risk modeling and space booster failure modes, not as a UAP observation report or resolu…

#event#official-source#war-gov

WAR.GOV D48 Air Force Report 1996

This page maps the D48 Air Force-report lane inside WAR.GOV / PURSUE Release 01. It represents DOW-UAP-D48, Department of the Air Force Report, 1996 as an official technical source on launch-risk modeling and space-booster failure modes, not as a UAP observation report or resolution finding. [S1][S2][S3][S4]

Related release navigation: release source page · file dossier index · investigation board · open questions · WAR.GOV · Department of War · United States Air Force · Vandenberg 2000 launch summary.

Quick facts

  • Official asset: DOW-UAP-D48, Department of the Air Force Report, 1996; Release 01 CSV row 57; agency Department of War; manifest incident date/location 9/10/96 / N/A. [S3][S4]
  • OCR custody: 181/181 pages with text, 270 OCR chunks, 438277 OCR characters, SHA-256 0dc72877cdf9cc3a1645c3c9d282928922b00e8fd9ffd7b1daf66f46c72b2071. [S2][S3]
  • Document identity: the OCR front matter identifies the file as RTI Report No. RTI/5180/77-43F, dated 10 September 1996, titled Modeling Unlikely Space-Booster Failures in Risk Calculations, prepared by James A. Ward, Jr. and Robert M. Montgomery for the Department of the Air Force 45th Space Wing Safety Office at Patrick AFB and 30th Space Wing Safety Office at Vandenberg AFB. [S5]
  • Release boundary: the graph/source pack found 0 graph lead relationships touching the D48 asset or manifest record at generation time; no conclusion nodes or relationship promotions were created. [S2]

Official asset spine

FieldValue
TitleDOW-UAP-D48, Department of the Air Force Report, 1996
Official URLofficial PDF
CSV row57
Manifest descriptionThis report describes the Modeling of Unlikely Space-Booster Failures in Risk Calculations, documenting historical launch failure modes and recommending corrective actions to address them using novel modelling techniques. [S4]
Local file custodyevidence/war-gov/war-gov-dow-uap-d48-department-of-the-air-force-report-1996-17a8cc07.md remains the per-asset wiki-page backlog; source pack preserves URL/hash/OCR fields. [S2][S3]
Review statusSource mapped; not a UAP case page; use for launch/satellite/missile/space-booster prosaic context only when a specific observation has time, location, and look-vector constraints. [S2]

Why this belongs in the release dossier

D48 is not a sighting report. Its value for Open Sky is that it gives official technical context for a family of ordinary-but-strange sky drivers: missile and space-vehicle failures, uprange or off-flight-line debris paths, range-safety modeling, and historical launch-performance records. Those are exactly the kinds of prosaic checks that must be exhausted before any launch-adjacent UAP report is escalated. [S5][S6][S7]

Claims extracted from official text

Claim layerWhat the corpus supportsReview status
Release manifestRelease 01 lists D48 as a Department-of-War PDF asset, CSV row 57, with incident date 9/10/96, location N/A, and a WAR.GOV PDF link. [S3][S4]source mapped
Report identityThe OCR front matter identifies the RTI final report, Air Force Space Command safety-office sponsors at Patrick AFB and Vandenberg AFB, report date 10 September 1996, and distribution limitations. [S5]source mapped; not a sighting
Mode-5 conceptThe report says less-likely missile/space-vehicle malfunctions can cause large deviations from intended flight lines and are modeled in DAMP as Mode-5 failure responses. [S6]technical context; no event identification
Launch-history basisThe report says it gathered and tabulated Atlas, Delta, Titan, and Thor launch/performance histories from Eastern and Western Ranges, assigning response modes and flight phases. [S7]review queue; OCR tables need verification
Probability/model outputsThe report presents recommended failure probabilities, response-mode percentages, absolute probabilities by response mode, and Mode-5 shaping-constant work. [S6]technical source; dated 1996
Future workThe report itself lists unfinished modeling improvements, including breakup conditions, stage cutoff timing, drag/free-fall modeling, sector size, and updated vehicle constants/probabilities. [S6]carry uncertainty forward
Graph relationship statusNo audit-only graph lead relationships were found for the D48 asset/manifest in this source pack. [S2]no crosslink promotion; no finding

Topical review queue

TopicWhat it supportsOpen Sky useBoundary
Report identity and custodyD48 is the 10 September 1996 RTI final report 'Modeling Unlikely Space-Booster Failures in Risk Calculations,' prepared for Department of the Air Force 45th Space Wing and 30th Space Wing safety offices. [S2][S5][S6][S7]Treat as an official technical source for launch-risk / booster-failure context, not as a sighting report.Release inclusion and official custody do not create a UAP finding.
Mode-5 failure conceptThe report says unusual space-booster malfunctions can send debris uprange or away from the intended flight line and models such responses in DAMP as Mode-5 failures. [S2][S5][S6][S7]Use as a prosaic-check reference when a sky report plausibly overlaps launch, missile-test, reentry, or booster-failure context.A Mode-5 model is not an identification of any released UAP record.
Empirical launch-history sampleThe report assembled Atlas, Delta, Titan, and Thor launch/performance histories from Eastern and Western Ranges and assigned response modes and flight phases for failures/anomalies. [S2][S5][S6][S7]Backlog candidate for a structured launch/failure-mode table after PDF-table and external-catalogue verification.OCR table rows are not yet a validated machine-readable launch database.
Probability estimates and response-mode percentagesThe report gives recommended failure probabilities and response-mode percentages, including Mode-5 percentages and absolute probabilities for Atlas, Delta, and Titan scenarios. [S2][S5][S6][S7]Useful for explaining why rare launch-failure modes remain in the prosaic checklist even when low probability.Those probabilities are model inputs for launch-risk analysis; they are not event-specific explanations.
Simulation and shaping constantsThe report simulated random-attitude and slow-turn malfunction cases and compared impact sectors to theoretical Mode-5 impact-density functions to choose shaping constants A and B. [S2][S5][S6][S7]Preserve as technical context for launch/plume/debris hypotheses and range-safety modeling.Do not overstate model precision or use it without observation geometry.
Future-investigation queueThe report itself lists unresolved modeling work: breakup conditions, stage cutoff timing, drag/free-fall treatment, sector size, and updating failure probabilities/new-vehicle constants. [S2][S5][S6][S7]Carry the report's own uncertainty forward into Open Sky's launch-correlation lane.The report is dated 1996; modern launch systems require updated sources before public explanatory use.

What can be said now

  • Release 01 contains an official Department-of-War-hosted PDF asset for a 1996 Department-of-the-Air-Force / RTI launch-risk report, with stable URL, SHA-256, and full OCR custody in Open Sky's source pack. [S2][S3]
  • The report is directly relevant to prosaic launch and space-vehicle checks because it models unusual booster failure responses, impact distributions, failure probabilities, and historical launch-performance records. [S5][S6][S7]
  • The report's appendix/history material can become a structured launch/failure-mode reference, but only after PDF-table verification and reconciliation with external launch catalogues. [S2][S7]
  • D48 does not by itself identify or resolve a UAP event. It is a background/reference source for launch-related hypotheses and source provenance. [S1][S2][S4]

What cannot be said yet

  • We cannot say D48 explains any particular UFO/UAP report without a target observation date/time, observer location, sky direction, and launch/trajectory/failure evidence. [S2]
  • We cannot treat Appendix D OCR as a finished launch database; tabular OCR needs PDF and external-catalogue checks before being used for public correlation. [S2][S7]
  • We cannot treat the 1996 risk model as current for modern launch systems without updated range-safety and launch-vehicle sources. The report itself lists future work and model uncertainties. [S6]
  • We cannot infer exotic significance from the release including D48. Its value here is provenance, technical context, and prosaic-check discipline. [S1][S2]

Watcher prosaic-check board

Check laneStatusNotes / next work
Astronomy / celestialNot started for a specific sightingD48 is not a sighting record. Run Moon/planet/star/meteor checks only after a target observation date, time, observer location, and sky direction are supplied. [S2]
Weather / atmospherePending / observation-dependentLaunch plume visibility, debris visibility, contrail/plume persistence, and sensor appearance depend on cloud cover, winds aloft, twilight geometry, humidity, and observer range. D48 does not supply those fields for any UAP report. [S2]
Satellites / reentries / launchesPartial source mappingThis is the core lane. D48 supplies historical launch-risk/failure-mode context, not a modern launch catalogue. Next step is structured extraction plus external launch-catalogue/range-source validation before any event-level correlation. [S6][S7]
Aircraft / drones / balloons / ordinary targetsPending / observation-dependentD48 is about missile/space-booster failure responses, not aircraft/drone/balloon observations. Use those lanes on paired sighting records. [S2]
Sensor / image-processing artifactsNot applicable to D48 itselfD48 is a document/text asset. Sensor-artifact checks belong to any paired image/video/sensor record. [S2]
Military / operational contextPartialThe report is sponsored by Air Force Space Command safety offices at Patrick AFB and Vandenberg AFB and covers Eastern/Western Range launch-performance history; exact operational context for any sighting still requires event-specific records. [S5][S7]

Selected source excerpts

IdxChunkExcerpt
0official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:0=== Page 1 === RESEARCH TRIANGLE INSTITUTE RTI Contract No. FO4703-91-C-0112 RTI Report No. RTI/5180/77-43F September 10, 1996 Modeling Unlikely Space-Booster Failures in Risk Calculations Final Report Prepared for Department of the Air Force 45th Space Wing (AFSPC) Safety Office - 45 SW/SE Patrick AFB, FL 32925 and Department of the Air Force 30th Space Wing (AFSPC) Safety Office - 30 SW/SE Vandenberg AFB, CA 93437 19961025 122 Distribution authorized to US Government agencies and their contractors to protect administrative/ operational use data, 10 September 96. Other requests for this document shall be referred to the 30th Space Wing (AFSPC) Safety Office (30 SW/SE), Vandenberg AFB, CA 93437, or 45th Space Wing (AFSPC) Safety Office (45 SW/SE), Patrick AFB, FL 32925. DTIC QUALITY INSPECTED 8 3000 N. Atlantic Avenue • Cocoa Beach, Florida 32931-5029 USA === Page 2 === 303O-TR-96-12 Contract No. FO4703-91-C-0112 RTI Report No. RTI/5180/77-43F Task No. 10/95-77, Subtask 2.0 September 10, 1996 Modeling Unlikely Space-Booster Failures in Risk Calculations Final Report Prepared by James A. Ward, Jr. Robert M. Montgomery of Research Triangle Institute Center for Aerospace Technology Launch Systems Safety Department Prepared for Department of the Air Force 45th Space Wing (AFSPC) Safety Office - 45 SW/SE Patrick AFB, FL 32925 and… [S2]
1official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:1SPC) Safety Office - 30 SW/SE Vandenberg AFB, CA 93437 Distribution authorized to US Government agencies and their contractors to protect administrative/ operational use data, 10 September 96. Other requests for this document shall be referred to the 30th Space Wing (AFSPC) Safety Officer (30 SW/SE), Vandenberg AFB, CA 93437, or 45th Space Wing (AFSPC) Safety Office (45 SW/SE), Patrick AFB, FL 32925. === Page 3 === REPORT DOCUMENTATION PAGE Form Approved OMB No. 0704-0188 Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. 1. AGENCY USE ONLY (Leave blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED September 10, 1996 Final 4. TITLE AND SUBTITLE 5. FUNDING NUMBERS Modeling Unlikely Space-… [S2]
2official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:222430 Hawthorne Blvd., Suite 300 RTI/5180/77-43F Torrance, CA 90505 9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING/MONITORING Department of the Air Force (AFSPC) Department of the Air Force (AFSPC) AGENCY REPORT NUMBER 30th Space Wing 45th Space Wing Vandenberg AFB, CA 93437 Patrick AFB, FL 32925 3O3O-TR-96-12 Mr. Martin Kinna (30 SW/SEY) Louis J. Ullian, Jr. (45 SW/SED) 11. SUPPLEMENTARY NOTES * Subcontractor ** Prime Contractor 12a. DISTRIBUTION/AVAILABILITY STATEMENT 12b. DISTRIBUTION CODE Distribution authorized to US Government agencies and their contractors to protect administrative/operational use data, 10 September 96. Other requests for this document shall be referred to the 30th Space Wing (AFSPC) Safety Office (30 SW/SE), Vandenberg AFB, CA 93437, or 45th Space Wing (AFSPC) Safety Office (45 SW/SE), Patrick AFB, FL 32925. C 13. ABSTRACT (Maximum 200 words) Missile and space-vehicle performance histories contain many examples of failures that cause, or have the potential to cause, significant vehicle deviations from the intended flight line. In RTI's risk-analysis program, DAMP, such failures are referred to as Mode-5 failure responses. Although Mode-5 failure responses are much less likely to occur than those that result in impacts near the flight line, risk-analysis studies are incomplete… [S2]
3official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:3. Certain Mode-5 malfunctions are simulated, and the two shaping constants then chosen by trial and error so that impacts from the simulated malfunctions and the theoretical density function are in close agreement. An appendix to the report contains a listing and brief narrative failure history of the Atlas, Delta, and Titan missile and space-vehicle launches from the Eastern and Western Ranges from the beginning of each program through August 1996. Each entry gives the vehicle configuration, whether the flight was a success, the flight phase in which any anomalous behavior occurred, and a classification of vehicle behavior in accordance with defined failure-response modes. 14. SUBJECT TERMS 15. NUMBER OF PAGES launch risk, unlikely failure modeling, booster failure probabilities 180 16. PRICE CODE 17. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 19. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACT OF REPORT OF THIS PAGE OF ABSTRACT Unclassified Unclassified SAR NSN 7540-01-280-5500 Standard Form 298 (Rev. 2-89) Prescribed by ANSI Std. Z39-18 298-102 === Page 4 === Abstract Missile and space-vehicle performance histories contain many examples of failures that cause, or have the potential to cause, significant vehicle deviations from the intended flight line. In RTI's risk-analysis program, DAMP, such failures are… [S2]
4official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:4simulated malfunctions and the theoretical density function are in close agreement. An appendix to the report contains a listing and brief narrative failure history of the Atlas, Delta, and Titan missile and space-vehicle launches from the Eastern and Western Ranges from the beginning of each program through August 1996. Each entry gives the vehicle configuration, whether the flight was a success, the flight phase in which any anomalous behavior occurred, and a classification of vehicle behavior in accordance with defined failure-response modes. Various filtering or data weighting techniques are described. The empirical data are then filtered to estimate (1) failure probabilities for Atlas, Delta, and Titan, and (2) percentages of future failures that will result in Mode-5 (and other Mode) responses. 9/10/96 i RTI === Page 5 === Table of Contents 1. Introduction...............................................................................................................1 2. Examples Showing Need for Mode 5 .......................................................................3 3. Understanding the Mode-5 Failure Response..........................................................7 3.1 Effects of Mode-5 Shaping Constants.................................................................9 3.2 Effects of Shaping Constant on DAMP… [S2]
5official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:56.1.4 Malfunction-Turn Results for Atlas IIAS....................................................35 6.2 Shaping Constants for Atlas IIAS.....................................................................37 6.2.1 Optimum Mode-5 Shaping Constants.........................................................37 6.2.2 Launch-Area Mode-5 Risks..........................................................................49 6.2.3 Effects of Mode-5 Constants on Ship-Hit Contours...................................51 6.2.4 Range Distributions of Theoretical and Simulated Impacts......................58 6.3 Shaping Constants for Delta-GEM...................................................................60 6.3.1 Optimum Mode-5 Shaping Constants.........................................................61 6.3.2 Launch-Area Mode-5 Risks..........................................................................64 6.4 Shaping Constants for Titan IV.........................................................................65 6.5 Shaping Constants for LLV1.............................................................................69 6.6 Shaping Constants for Other Launch Vehicles.................................................73 7. Potential Future Investigations..............................................................................73 8.… [S2]
10official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:1041. Atlas Launch History ........................................................................................ 103 Table 42. Summary of Delta Vehicle Configurations ..................................................... 133 Table 43. Delta Launch History ........................................................................................ 136 Table 44. Summary of Titan Vehicle Configurations ..................................................... 147 Table 45. Titan Launch History ........................................................................................ 149 Table 46. Thor Launch History.......................................................................................... 165 9/10/96 vi RTI === Page 10 === 1. Introduction The debris from most launch vehicles that fail catastrophically tend to impact close to the intended flight line. Typical failures that produce such results are premature thrust termination, stage ignition failure, tank rupture or explosion, or rapid out-of-control tumble. Less likely malfunctions may cause a vehicle to execute a sustained turn away from the flight line. Examples are control failures that cause the rocket engine to lock in a fixed position near null, or failures leading to erroneous orientation of the guidance platform. Such failures should not be ignored, since they may… [S2]
17official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:17As still another example of a Mode-5 failure response, a guided Red Tigress sounding rocket was launched from Pad 20 at Cape Canaveral on 20 Aug 91. Within a second or two after clearing the launcher, the rocket made a near 90° right turn, and flew stably in this direction until destroyed by the safety officer at 23.3 seconds. Pieces impacted some two or three miles from the launch pad. This failure might have been classified as a Mode-2 response if destruct action had been taken shortly after launch. 9/10/96 6 RTI === Page 16 === 3. Understanding the Mode-5 Failure Response Unlike failure response Modes 3 and 4, response Mode 5 (and also Mode 2) is not a direct function of time from launch. For Modes 3 and 4, the mean point of impact (MPI) for each debris class is fixed, once the failure time is established. At each instant there is only one possible location for the MPI for each debris class. On the other hand, the Mode-5 impact-density function for each debris class consists of a primary part and a secondary superimposed part. The primary impact-density function accounts for impact variability due to the erratic flight of the vehicle. It is used to determine the probability that the mean piece in a debris class resulting from vehicle breakup falls in a given area (say on a building or open field). The secondary density… [S2]
47official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:47compromise between new and mature liquid-propellant vehicles, a value of F = 0.996 has been assumed for new solid-propellant vehicles. The percentages shown in Table 15 for flight phases 0 - 2 have been obtained from Table 14. Similar information for flight phases 0 - 1 are given in Table 16. In future risk studies for the 45 SW/SE, RTI plans to use these relative percentages for mature and new systems. Table 15. Recommended Response-Mode Percentages for Flight Phases 0 - 2 | Response Mode | Mature Launch Systems (F = 0.993) | New Solid Systems (F = 0.996) | New Liquid Systems (F = 0.999) | |---|---|---|---| | 1 | 0.4 | 2.2 | 7.4 | | 2 | 5.4 | 4.5 | 2.5 | | 3 | 0.1 | 0.4 | 1.7 | | 4 | 86.2 | 80.4 | 73.3 | | 5 | 7.9 | 12.7 | 15.3 | 9/10/96 28 RTI === Page 38 === Table 16. Recommended Response-Mode Percentages for Flight Phases 0 - 1 | Response Mode | Mature Launch Systems (F = 0.993) | New Solid Systems (F = 0.996) | New Liquid Systems (F = 0.999) | |---|---|---|---| | 1 | 0.5 | 3.4 | 10.7 | | 2 | 7.4 | 6.6 | 4.3 | | 3 | 0.1 | 0.6 | 2.4 | | 4 | 81.9 | 74.5 | 67.0 | | 5 | 10.1 | 14.9 | 15.6 | Absolute probabilities of occurrence for response Modes 1 through 5 can be obtained by multiplying the absolute failure probabilities for flight phases 0 - 1 and 0 - 2 (Table 6) by the relative failure probabilities in Table 15 and Table 16.… [S2]
48official:doc:war-pursue-uap-release:asset:dow-uap-d48-report-september-1996-pdf:17a8cc07fd8c:frontier-ocr:chunk:48occurrence for response Modes 1 through 5 can be obtained by multiplying the absolute failure probabilities for flight phases 0 - 1 and 0 - 2 (Table 6) by the relative failure probabilities in Table 15 and Table 16. The results are shown in Table 17. Probabilities are listed to six decimal places to show differences, not because all figures are actually significant. To obtain these results, more precise values for relative probabilities of occurrence were used than shown in Table 15 and Table 16. Table 17. Absolute Failure Probabilities for Response Modes 1 - 5 | Vehicle: | Atlas | | Delta | | Titan | | |---|---|---|---|---|---|---| | Flight Phase: | 0 - 1 (0-170 sec) | 0 - 2 (0-280 sec) | 0 - 1 (0-270 sec) | 0 - 2 (0-630 sec) | 0 - 1 (0-300 sec) | 0 - 2 (0-540 sec) | | Mode 1 | 0.000119 | 0.000121 | 0.000054 | 0.000051 | 0.000216 | 0.000250 | | Mode 2 | 0.001637 | 0.001665 | 0.000744 | 0.000698 | 0.002976 | 0.003437 | | Mode 3 | 0.000011 | 0.000012 | 0.000005 | 0.000005 | 0.000020 | 0.000026 | | Mode 4 | 0.018007 | 0.026738 | 0.008185 | 0.011212 | 0.032740 | 0.055200 | | Mode 5 | 0.002226 | 0.002465 | 0.001012 | 0.001034 | 0.004048 | 0.005088 | | Total | 0.022 | 0.031 | 0.010 | 0.013 | 0.040 | 0.064 | For each vehicle, the absolute probabilities for Modes 1, 2, and 3 differ slightly for flight phase 0 - 1 and 0 - 2. This… [S2]

Open questions

  1. Should Appendix D be parsed into a structured Atlas/Delta/Titan/Thor launch-failure reference table, or should Open Sky only extract rows that collide with existing case pages? [S2][S7]
  2. Which existing launch/plume/missile-test candidate pages in the wiki should be checked against D48 and D49 Vandenberg together? [S2]
  3. Which external catalogues should anchor validation before any explanatory use: launch logs, payload catalogs, range histories, orbital catalogs, DTIC report metadata, or all of the above? [S2][S7]
  4. Does D48's dated model need a modern counterpart source before the public explorer presents launch-failure probabilities or Mode-5 context? [S6]

Evidence and provenance handling

  • Source pack: internal Open Sky cache/report and .json.
  • Generated at 2026-05-09T14:01:13.515359+00:00 from read-only Neo4j queries and the Release 01 asset inventory. [S2]
  • Per-asset wiki page remains the generated backlog path listed in the asset index: evidence/war-gov/war-gov-dow-uap-d48-department-of-the-air-force-report-1996-17a8cc07.md. [S2]
  • This page should be linked from the release MOC, the investigation board, open questions, and the release source page.

Sources cited

  • [S1] Official WAR.GOV landing page: https://www.war.gov/UFO/; official CSV manifest: https://www.war.gov/Portals/1/Interactive/2026/UFO/uap-csv.csv.
  • [S2] Generated source pack: internal Open Sky cache/report, built from Neo4j dataset war_pursue_uap_release_2026_05_08 and internal Open Sky cache/report at 2026-05-09T14:01:13.515359+00:00.
  • [S3] Official asset DOW-UAP-D48, Department of the Air Force Report, 1996: https://www.war.gov/medialink/ufo/release_1/dow-uap-d48-report-september-1996.pdf; SHA-256 0dc72877cdf9cc3a1645c3c9d282928922b00e8fd9ffd7b1daf66f46c72b2071; OCR custody 181/181 pages with text, 270 OCR chunks.
  • [S4] Release 01 CSV/manifest record for row 57 and graph manifest record official:doc:war-pursue-uap-release:record:afb5fd0d95de1502.
  • [S5] D48 OCR front-matter excerpts in source pack [S2], especially frontier OCR chunks 0–3 identifying the report title, authors, sponsoring Air Force offices, report date, abstract, and distribution statement.
  • [S6] D48 selected OCR modeling/probability excerpts in source pack [S2], especially frontier OCR chunks 10, 17, 47–48, and 88–96 for Mode-5, DAMP, failure probabilities, shaping constants, summary, and future investigations.
  • [S7] D48 selected OCR launch-history excerpts in source pack [S2], especially frontier OCR chunks 134, 202, 222, and 256 for Atlas, Delta, Titan, and Thor history tables.
  • [S8] Graph-safety check in source pack [S2]: graph lead count for D48 asset/manifest was 0; no relationship promotion and no conclusion-node writes.