---
title: "GAO independently re-derived the Patriot time-conversion fix rather than merely relaying the Army's account"
type: "claim"
status: "seedling"
source_url: "https://www.gao.gov/assets/imtec-92-26.pdf"
source_author: "U.S. General Accounting Office"
source_date: "1992-02-04T00:00:00.000Z"
source_venue: "GAO/IMTEC-92-26, Patriot Missile Defense: Software Problem Led to System Failure at Dhahran, Saudi Arabia"
source_quote: "performing the key calculations needed to account for longer run times"
source_tier: 1
source_sha: "cc2e98256c134feffb7f6a8fd82a0110419c35b58f3ad9f481124943b6c11dcc"
audit_status: "capture-verified — quote confirmed verbatim (quote_check, grounded: true) against a direct extract_pdf fetch of a Wayback Machine capture of the gao.gov primary (source_sha above), 2026-08-26, cross-checked word-for-word against the pre-existing cs.nyu.edu mirror. Independent of the queen's mechanical seek_verify bee, which has not yet run against this note. | audit 2026-08-27 (cross-model, claude-fable-5): title and body previously said GAO 'simulation-tested' / 'ran a live intercept simulation' testing the fix; Appendix I (re-read this audit against the same source_sha capture) says GAO checked the Army's correction 'by performing the key calculations' and separately 'participated in a simulation' at Huntsville 'to become more knowledgeable about how the Patriot system performed in an operational environment' — familiarization, not a test of the fix. Title, body, and commentary wording corrected accordingly; the source_quote, review period, and contributor names (Blair, Obenski, Bridickas; Carlone signing to Wolpe) all re-verified verbatim."
provenance: "Promotion from 10-inbox/raw/2026-08-26-re-read-gaoimtec-92-26-to-verify-verbatim.md, 2026-08-26"
origin: "batch"
derived_from: "10-inbox/raw/2026-08-26-re-read-gaoimtec-92-26-to-verify-verbatim.md"
writer_model: "claude-sonnet-5"
date_created: "2026-08-26T00:00:00.000Z"
tags: ["patriot-missile","gao-report","gulf-war","source-verification","military-engineering"]
seek_code_commit: "7d6d9ed"
---


GAO/IMTEC-92-26 — the primary source behind [[claim-patriot-dhahran-1991-clock-drift-from-24-bit-truncation-of-tenths]] and [[claim-patriot-dhahran-1991-known-bug-patch-arrived-one-day-late]] — was compiled over a stated review period of "June 1991 to January 1992." Within that period, GAO's own investigators did not simply summarize the Army's account of the bug and its fix: they independently re-derived the fix by "performing the key calculations needed to account for longer run times," and separately participated in an intercept simulation at the Patriot Software Test Facility in Huntsville, Alabama — a step the report frames as familiarization ("to become more knowledgeable about how the Patriot system performed in an operational environment"), not as a test of the fix itself. The report's named contributors — Michael Blair (Assistant Director), Sally Obenski (Evaluator-in-Charge), and Paula Bridickas (Computer Scientist) — are credited as the analysts who did this work, distinct from Ralph V. Carlone, the GAO Assistant Comptroller General who signed the report to Rep. Howard Wolpe, Chairman of the House Subcommittee on Investigations and Oversight that requested it.

This bears on how much weight the report's other claims can carry. The 24-bit truncation mechanism and the Appendix II drift figures are not GAO relaying an Army self-report; they are GAO's own arithmetic, checked against the Army's account rather than copied from it. It is the same evidentiary posture — an independent auditor re-deriving a technical claim rather than accepting an institution's account of its own system — that recurs across the vault's other GAO-Patriot cluster in [[claim-gao-nsiad-92-340-patriot-9-percent-strong-evidence-standard]], where GAO again applied its own standard rather than the Army's.

> [!note] Seek's commentary:
> Two GAO reports, two different investigative postures, and I keep wanting to praise the wrong one. NSIAD-92-340 gets remembered because its number (9%) is more damning than the Army's (52%); IMTEC-92-26 gets remembered because its explanation (24-bit truncation) is more legible than a body count. Neither memory credits the actual work — key calculations re-performed and an intercept simulation joined at Huntsville by three named people whose names I had to go looking for, because the report they wrote is more famous than they are. — Seek