FILE DEPT

Field Report Archive

Private Skeptical Evidence Corpus

← Back to Case Files

UAP / Balloon Incident
Single-Record File

FAA Report 237UAP00010: Helium Balloon Sighting near Denver

Single-Record File: Only one inspectable record is attached. It documents a source or allegation but cannot independently corroborate the broader claim.
2009-10-16
18 NM North of Denver, Colorado, USA
10/10
1/10
A helium-filled home-made balloon, feared to have a six-year-old child aboard, was tracked to a soft landing.
low

Investigative Assessments

"The reported claim remains worth testing against the record: A helium-filled home-made balloon, feared to have a six-year-old child aboard, was tracked to a soft landing. The strongest documented reasons to keep the file open are: FAA SKYWATCH Incident Form 237UAP00010: Documents a pilot report of A helium-filled home-made balloon, feared to have a six-year-old child aboard, was tracked to a soft landing.. Key unresolved lead: Why did the FAA coordinate helicopter tracking and TFR planning before verifying if the child was aboard?"
"Evidentiary limitations: low Note that: FAA SKYWATCH Incident Form 237UAP00010 fails to support: The operational log does not contain physical telemetry, radar recordings, or photos to independently verify the nature of the object.."

Case Summary

An intake summary of FAA operational log 237UAP00010 recording an aircrew reporting an unidentified aerial phenomenon. A helium-filled home-made balloon, feared to have a six-year-old child aboard, was tracked to a soft landing. This pilot synopsis is an intake summary requiring source-by-source verification.

Evidence Locker

1 inspectable evidence item. Claims and source findings are kept separate.

FAA incident report Local copy hash-verified

FAA SKYWATCH Incident Form 237UAP00010

Analyst rating: Primary operational record of an aircrew report and the FAA's contemporaneous assessment.

“1730: Father called ZDV directly to inform ATC that his six year old son had gone airborne in a helium filled balloonthat he had made to resemble a UFO, which was previously anchored at the family's home. 1845: ZDV called to advise DEN of situation. 1855: D.E.N. requested D01 and COS come up on the DEN. Local LEOs aware of the situation. D01 is working chase plane which will relay periodic updates. 1857: Balloon 18N of DEN @ 12,000-13000ft.The balloon was airborne for approximately 30-miles and reached a height of nearly 13,000ft. A TV helo tracked the balloon for almost the entirety of its flight. Two ANG helos joined in on thetrail at around the 15-mile point of the flight. The balloon descended slowly during the last 10-15-miles of its flight. The balloon landed softly in a clearing on the DEN026@10.4-miles. As of 2024Z there still hasn't been any sign of the missing child. The DEN/SOSCs have accumulated the data (ADAPT track data history and print outs, along with potential locations requiring TFRs for SAR missions.) TSOC will advise the moment they hear from local LEOs when/if the child is located. 2121: As the TV pictures shown never depicted a basket on the balloon, we queried ZDV to check data to see where the TV helo first engaged the Balloon. The determination was that the helo first filmed the balloon within 1-1.5-miles of the launch site (child's home). ZDV has forwarded the information to the proper authorities for the possible SAR. None of our resources have the ability to depict altitude data due to the ACFT being without an operating transponder or mode-c readout. FYSA: It has been noted that the family of the boy who was reported by his father to be aboard the balloon has in the past been part of a Reality TV show. 2210: CNN reports boy found at home, safe and was never aboard the balloon.”
Record locationPage 1
Evidence classFAA operational incident record
Relationship to claimPrimary document recording the pilot's intake report.
Authenticity assessmentHigh for document authenticity. The one-page FAA form was visually checked against the NARA PDF.
What this supportsDocuments a pilot report of A helium-filled home-made balloon, feared to have a six-year-old child aboard, was tracked to a soft landing.
What it does not supportThe operational log does not contain physical telemetry, radar recordings, or photos to independently verify the nature of the object.
ProvenanceOfficial NARA UAP bulk-download record, hash-registered in the Casebook manifest and served from the read-only VPS corpus mount.
Chain of custodyAircrew report -> FAA SKYWATCH incident form -> FAA transfer to NARA Record Group 615 -> NARA bulk archive -> Casebook.

Documented Timeline

Not documented: No source-verified chronology has been assembled.

Named Participants and Roles

Not documented: Named participants and roles have not been source-verified.

Contradictions and Record Conflicts

Not documented: Record conflicts have not been analyzed.

Conventional Explanations

Not documented: Conventional explanations have not been evaluated against evidence.

Missing Evidence

Not documented: The evidence gap itself has not yet been fully inventory.

What Remains Unresolved

Not documented: No source-level unresolved findings have been established.

Investigative Hypotheses

  • A helium-filled promotional or experimental balloon launched as a hoax.
  • A misidentified conventional weather balloon.
  • An amateur scientific launch.

Open Questions

  • Why did the FAA coordinate helicopter tracking and TFR planning before verifying if the child was aboard?
  • What radar signature did the balloon produce without a transponder?
  • How did the television coverage affect the emergency response coordination?

Archival Landing Pages and Evidence Corpus

NARA Record Group 615, FAA UAP Records

Official Bulk Archive

External URL: https://catalog.archives.gov/id/493468575