WELL · 42-331-32972 · DISTRICT 1
Huber-Perry #1
Milam County · Milbur (Navarro) field · NO Production · Vertical
Huber-Perry #1 (API 42-331-32972) is a well in Milam County operated by Blue Flame Operating Company LLC, completed January 22, 1985 and listed as no production on the RRC schedule.
The RRC has issued one drilling permit, issued September 20, 1985, permitted to 4,400 ft.
It was permitted by Leonard, J. A. and has since transferred to Blue Flame Operating Company LLC on the wellbore schedule.
Completion filings report 2 formation tops, including Wilcox, Navarro.
Its lease has reported 3.35K barrels of oil and 5.47K mcf of gas since January 1993, last reporting in July 2026.
Operator of record
Blue Flame Operating Company LLC
Permitted by Leonard, J. A.; the EWA schedule now lists a different operator.
Austin, TX · P-5 Y, filed Aug 4, 2025 · 1 permits on file · (512) 590-2522
SOURCE · RRC EWA WELLBORE SCHEDULE
- 4,400
- total depth, ft
- 1
- permits on file
- Sep 20, 1985
- last permit issued
- Jan 22, 1985
- completed
- 3.35K
- cumulative oil, bbl
- 5.47K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jan 22, 1985
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Delinquent
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 |
|---|---|---|---|---|---|---|
| Huber-Perry O-1-11339 | Milbur (Navarro) | Blue Flame Operating Company LLC | 1 | 3.35K | 5.47K | Jan 1993 – 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.
- 1Houston Petroleum CompanyAug 2001 → Jul 2017
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 285581-99 | Drill | Leonard, J. A. | Sep 19, 1985 | Sep 20, 1985 | — | 4,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-11339 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 485 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,389 | 3,402 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 479 | 12.25 | 315 S |
| 4.5 | 3,730 | 7.875 | 700 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 | Feb 18, 1986 | Feb 3, 1986 | Yes |
| 00 | Feb 12, 1986 | — | — |
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-331-32972 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-331-32972 → 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/33132972, documented in the API reference.