TEXAS · WELLS · ROBERTSON COUNTY · WHITETAIL UNIT LEASE · API 42-395-30538 · DISTRICT 03
Whitetail Unit #1
Robertson County · Giddings (Buda) field · Shut In · Horizontal · Sidetrack
Whitetail Unit #1 (API 42-395-30538) is a horizontal well in Robertson County operated by Wildfire Energy Operating LLC, completed July 23, 1998 and listed as shut in on the RRC schedule, shut in June 1, 2020.
The RRC has issued 3 drilling permits (amended twice) between 1997 and 1998, permitted to 6,942 ft.
It was permitted by Union Pacific Resources Company and has since transferred to Wildfire Energy Operating LLC on the wellbore schedule.
Completion filings report 4 formation tops, including Austin Chalk, Buda, Del Rio, Georgetown.
Its lease has reported 53.4K barrels of oil and 53.5K mcf of gas since November 1997, last reporting in July 2026.
Operator of record
Permitted by Union Pacific Resources Company; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Nov 24, 2025
- Permits on file
- 171
- Phone
- (832) 558-0100
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Wildfire Energy Operating LLC |
| Production reports | Chesapeake Operating, L.L.C.through Sep 2019 |
| Latest permit | Union Pacific Resources CompanyOct 28, 1998 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 6,942
- total depth, ft
- 5
- permits on file
- Oct 28, 1998
- last permit issued
- Jul 23, 1998
- completed
- 53.4K
- cumulative oil, bbl
- 53.5K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 1997 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jul 23, 1998
- Shut in
- Jun 1, 2020
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
Surface location
No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH APR 2026
Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Whitetail Unit O-3-23377 | Giddings (Buda) | Wildfire Energy Operating LLC | 1 | 53.4K | 53.5K | Nov 1997 – Jul 2026 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Union Pacific Resources CompanyNov 1997 → Jan 2001
- 2Rme Petroleum CompanyFeb 2001 → Nov 2002
- 3Anadarko E&P Company LPDec 2002 → Dec 2012
- 4Anadarko E&P Onshore LLCJan 2013 → Jul 2014
- 5Williams, Clayton Energy, Inc.Aug 2014 → Nov 2016
- 6Wildhorse Resources Mngt Co, LLCDec 2016 → Mar 2019
- 7Chesapeake Operating, L.L.C.Jun 2019 → Sep 2019
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 480412-99 | Recompletion · sidetrack | Union Pacific Resources Company | Oct 23, 1998 | Oct 28, 1998 | Jun 25, 1998 | 7,500 |
| 472545-98 | Recompletion · sidetrack | Union Pacific Resources Company | Aug 31, 1998 | Jan 22, 1998 | — | 7,500 |
| 472545-99 | Recompletion · sidetrack | Union Pacific Resources Company | Jan 22, 1998 | Jan 22, 1998 | Jan 25, 1998 | 6,500 |
| 467775-98 | Drill | Union Pacific Resources Company | Dec 11, 1997 | Sep 19, 1997 | — | 7,700 |
| 467775-99 | Drill | Union Pacific Resources Company | Sep 19, 1997 | Sep 19, 1997 | Oct 2, 1997 | 7,700 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jul 23, 1998 | Whitetail Unit O-3-23377 | Giddings (Buda) | Wildfire Energy Operating LLC | Shut In · shut in Jun 1, 2020 | 6,942 |
| Jul 23, 1998 | Whitetail Unit O-3-23377 | Giddings (Buda) | Wildfire Energy Operating LLC | Shut In · shut in Jun 1, 2020 | 6,942 |
Formation tops
As filed on W-2/G-1. Subsea from 259 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Austin ChalkTOP AUSTIN CHALK | 6,068 | -5,809 |
| Buda | 6,614 | -6,355 |
| Buda | 6,667 | -6,408 |
| Del Rio | 6,733 | -6,474 |
| Georgetown | 6,763 | -6,504 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,608 | 11,420 | Perforated |
| 6,609 | 11,160 | Perforated |
| 6,611 | 12,125 | Perforated |
| 6,713 | 7,332 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 810 | 14.75 | 590 S |
| 7.625 | 6,825 | 9.875 | 280 S |
| — | 6,825 | 9.875 | 280 S |
| 7.625 | — | 9.875 | 500 S |
Completion filings
W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Oct 6, 1998 | Aug 12, 1998 | Yes |
| 00 | Oct 2, 1998 | May 29, 1998 | — |
| 00 | Jan 28, 1998 | Dec 11, 1997 | Yes |
| 00 | Jan 20, 1998 | — | — |
The source documents
Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.
- Wellbore filings for 42-395-30538 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-395-30538 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.
About this data
Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.
New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease
Developers: this page as JSON is GET /v1/data/wells/39530538, documented in the API reference.