TEXAS · WELLS · BROOKS COUNTY · API 42-047-32116 · DISTRICT 04
Tres Puertas #12
Brooks County · Wildcat field · Vertical
- Fields on the latest permit · any of 17
- Alta Mesa N. (600) · Field 2002090 · Field 2002099 · Alta Mesa, N. (1100) · Alta Mesa, N. (1500) · Field 2002285 · Alta Mesa, N. (1700) · Field 2002444 · Alta Mesa, N. (2000) · Field 2002666 · Field 2002710 · Alta Mesa, N. (2600) · Alta Mesa, N. (2940) · Alta Mesa, N. (3650) · Alta Mesa, N. (4100) · Field 2002800 · Alta Mesa N. (4350)
- Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.
Tres Puertas #12 (API 42-047-32116) is a plugged well in Brooks County, plugged February 2, 2004, last operated by Mestena Operating Ltd..
The RRC has issued one drilling permit, issued November 13, 2003, permitted to 11,000 ft.
It was permitted by Mestena Operating, Ltd. and has since transferred to Mestena Operating Ltd. on the wellbore schedule.
Operator of record
Mestena Operating Ltd.
Permitted by Mestena Operating, Ltd.; the EWA schedule now lists a different operator.
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Mestena Operating, Ltd.Nov 13, 2003 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 11,000
- total depth, ft
- 1
- permits on file
- Nov 13, 2003
- 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
- Feb 2, 2004
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.
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 |
|---|---|---|---|---|---|---|
| 538551-99 | Drill | Mestena Operating, Ltd. | Nov 13, 2003 | Nov 13, 2003 | Nov 25, 2003 | 11,000 |
Well logs
1 log loaded from the RRC's log index, the latest received Feb 12, 2007. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| ResistivityARRAY INDUCTION DENSITY NEUTRON FINAL COMPOSITE | TIFF | 6,274 to 8,886 | Feb 12, 2007run Nov 26, 2003 | — |
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-047-32116 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-047-32116 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/04732116, documented in the API reference.