# TEXAS BIGFOOT UP CLOSE! Page: https://stenobird.com/podcast/ufo-warning-71498/texas-bigfoot-up-close Text version: https://stenobird.com/podcast/ufo-warning-71498/texas-bigfoot-up-close.md Podcast: [UFO WARNING](https://stenobird.com/podcast/ufo-warning-71498) Published: 2026-05-01T16:23:35+00:00 Episode link: https://podcasters.spotify.com/pod/show/ufo-warning/episodes/TEXAS-BIGFOOT-UP-CLOSE-e3ioi8u Audio file: https://traffic.megaphone.fm/APO1972361074.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/ufo-warning-71498/episodes/texas-bigfoot-up-close Duration seconds: 1304 ## Resource In this chilling episode of UFO Warning , we investigate a close-range Bigfoot sighting in Texas that left multiple witnesses stunned. On the night of March 15, 2024 , a couple driving along FM 312 near Winnsboro encountered a massive, upright creature illuminated in their headlights—estimated to be over 7 feet tall , with long arms and thick reddish-brown hair. Initially mistaken for livestock, the figure quickly revealed itself as something far more mysterious as it moved toward the tree line just feet from the road. Both witnesses describe a powerful build, unusually broad shoulders, and deliberate movement before the creature disappeared into the woods. We break down the full encounter, including investigator insights, environmental factors, and why this region of East Texas—situated between major water sources and dense wooded corridors—has become a hotspot for Sasquatch sightings . Was this a misidentified animal… or a genuine Bigfoot encounter ? ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/ufo-warning-71498/episodes/texas-bigfoot-up-close/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/ufo-warning-71498/texas-bigfoot-up-close.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.