/ufo/reeves-field/
28,665 views
bf-0320 SECRET NOT BROOKSVILLE

REEVES FIELD

Reeves Field. Naval auxiliary strip and thinner unnamed nights over water. Exists so Brooksville's John F. Reeves cannot be welded to a catapult. Different job. Different dirt.

Report ID bf-0320
Clearance SECRET
Category UFOs & NHI
Status NOT BROOKSVILLE
Timestamp 2026-09-13 19:18 UTC
Coordinates 33°45'00 N
118°15'00 W

1. Public Record

Reeves Field. A naval auxiliary strip in the compiler stacks: lights over water, a night that did not produce a wreck, a name that search engines will try to weld to John F. Reeves of Brooksville. This page exists to break that weld. Brooksville is 2 March 1965 and a dropped sheet. Reeves Field is a runway and a thinner naval hour. Different job. Different dirt.

Naval fields generate unknowns the way NORAD holes do. That is the cheap close. It is also why a named strip still earns a card: so Brooksville does not have to carry a catapult and a coastline it never owned.

A strip. Water. A surname already used this batch.

Auxiliary fields live in footnotes. That is why they pick up stray nights. This card accepts the thinness. It will not accept Brooksville's page as a logbook.

Write the split twice if you have to. Weld once and both files rot.

2. Date of Incident

Naval nights as carried in compiler lists. No single date this folder will force onto the strip.

3. Location

Naval auxiliary / Reeves Field as named in the stacks. Water adjacent. Coordinates unforced rather than invented.

4. Official Narrative

Working naval field weather. Official narrative is absence of a typed airframe on the nights that stay unnamed.

5. Witness Layer

Naval crews and tower as later listed. John F. Reeves as neighbouring surname only.

Cheap and true can sit together. They still do not type the light.

A dropped page is not a catapult. Keep the inventory honest.

6. Recovery Logistics

No public wreck. No Brooksville sheet on this dirt.

7. Assessment

Start with the surname problem. This folder is a divider first and a case second. The naval hour is thinner than Falconbridge and thinner than Goose Bay. That is allowed. Thin is not empty if it stops a weld.

This folder files Reeves Field as a naval-strip card. Keep Brooksville as 0316. Keep the light untyped. No tray.

Thin cards earn their number when they stop a weld. That is this card's whole job. The nights can stay unnamed.

Auxiliary strips sit in footnotes next to bigger carriers. Footnotes collect stray lights. This page accepts that thinness and still refuses Brooksville's sheet as a deck log. A dropped page is not an approach radar. Keep the catapult off the scrub.

8. Materials & Remains

Compiler nights. No hardware.

9. Key Personnel

Naval tower and crews as listed : The strip.

John F. Reeves : Neighbouring card only.

10. Aftermath

Search engines keep welding. This page keeps cutting. The strip does not become Brooksville.

11. Current Archive Status

Status: Strip. Not Brooksville.

Confidence: High that a Reeves Field naval name exists apart from John F. Reeves. Low that any one night is typed. High that the weld is the danger.

If a later stack publishes a dated deck log with a Reeves Field header and a night, this card can grow a date. Until then the header is the point: naval, not Brooksville, not a language sheet walking out of palmetto.

Filing note

A naval strip, water, unnamed lights, a Florida retiree on this shelf with the same surname and a page in his hand, a weld this card exists to cut.

Different job. Different dirt. That is the only reason the field gets a number.

bf-0320
boringfolder