WELL · 42-323-33633 · DISTRICT 1
WTG303 #1
Maverick County · Vertical
Wtg303 #1 (API 42-323-33633) is a permitted well in Maverick County filed by West Texas Gas Utility, LLC; no completion report is on file yet.
The RRC has issued one drilling permit, issued February 21, 2024, permitted to 400 ft.
Operator of record
Midland, TX · P-5 Y, filed Sep 4, 2025 · 4 permits on file · (866) 504-0407
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | West Texas Gas Utility, LLCFeb 21, 2024 |
- 400
- total depth, ft
- 1
- permits on file
- Feb 21, 2024
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
Surface location
28.965649, -100.408789
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Maverick County.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 897088-99 | Drill | West Texas Gas Utility, LLC | Feb 5, 2024 | Feb 21, 2024 | — | 400 |
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-323-33633 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-323-33633 → 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.
Nearby wells and their tops
NEAREST 5 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well has no tops filed, so it cannot anchor a section; its neighbours can.
Paloma "E"42-323-32512
5.4 KM · Field Petroleum Corp. · Section with this well →
| Austin Chalk | 800 | 98 |
| Eagle Ford | 1,708 | -810 |
| Del Rio | 2,318 | -1,420 |
| Georgetown | 2,560 | -1,662 |
| Edwards | 3,500 | -2,602 |
| Glen Rose | 3,920 | -3,022 |
Burr C 560442-323-33456
11.5 KM · Newfield Exploration Company · Section with this well →
| Eagle Ford | 1,380 | -466 |
| Eagle Ford | 1,555 | -641 |
| Buda | 1,735 | -821 |
| Del Rio | 1,865 | -951 |
| Georgetown | 2,100 | -1,186 |
| San Miguel | — | |
| Edwards | — | |
| McKnight | — |
10 TOPS · FIRST 8
Paloma "B"42-323-32483
12.4 KM · Field Petroleum Corp. · Section with this well →
| Austin Chalk | 910 | 1,019 |
| Eagle Ford | 1,800 | 129 |
| Buda | 2,440 | -511 |
| Del Rio | 2,597 | -668 |
| Georgetown | 2,855 | -926 |
| McKnight | 3,605 | -1,676 |
Paloma42-323-32391
12.8 KM · Field Petroleum Corp. · Section with this well →
| Austin Chalk | 970 | -68 |
| Eagle Pass | 1,980 | -1,078 |
| Buda | 2,484 | -1,582 |
| Del Rio | 2,640 | -1,738 |
| Georgetown | 2,900 | -1,998 |
| Pearsall | 6,500 | -5,598 |
Paloma42-323-32772
14.3 KM · Field Petroleum Corp. · Section with this well →
| Anacacho | 781 | 76 |
| Austin Chalk | 988 | -131 |
| Eagle Ford | 1,833 | -976 |
| Buda | 2,476 | -1,619 |
| Del Rio | 2,694 | -1,837 |
| Georgetown | 2,947 | -2,090 |
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/32333633, documented in the API reference.