WELL · 42-479-41456 · DISTRICT 4
BMT #20QC
Webb County · Laredo S. (Queen City) field · Temp Abandoned · Vertical
Bmt #20QC (API 42-479-41456) is a well in Webb County operated by Columbus Energy LLC, completed December 6, 2011 and listed as temp abandoned on the RRC schedule.
The RRC has issued one drilling permit, issued August 26, 2011, permitted to 2,200 ft.
Completion filings report 2 formation tops, including Eagle Ford, Marker 2.
No lease production has been reported under this well’s leases.
Operator of record
Houston, TX · P-5 Y, filed Apr 4, 2026 · 51 permits on file · (956) 722-5238
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Columbus Energy LLC |
| Production reports | Columbus Energy, LLCthrough Apr 2017 |
| Latest permit | Columbus Energy, LLCAug 26, 2011 |
- 2,200
- total depth, ft
- 1
- permits on file
- Aug 26, 2011
- last permit issued
- Dec 6, 2011
- completed
- 0
- cumulative oil, bbl
- 50.9K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 2011 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Dec 6, 2011
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: X
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 |
|---|---|---|---|---|---|---|
| BMT G-4-263808 | Laredo, S. (Queen City) | Columbus Energy, LLC | 1 | 0 | 50.9K | Dec 2011 – 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.
- 1Columbus Energy, LLCDec 2011 → Apr 2017
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 722950-99 | Drill | Columbus Energy, LLC | Aug 23, 2011 | Aug 26, 2011 | Oct 18, 2011 | 2,200 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-263808 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 399 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Eagle FordEAGLEFORD | 1,192 | -793 |
| Marker 2 | 1,428 | -1,029 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,199 | 1,240 | Perforated |
| 1,429 | 1,433 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 160 | 12.25 | 70 S |
| 4.5 | 1,606 | 7.875 | 319 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 | Jun 15, 2012 | Jan 24, 2012 | Yes |
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-479-41456 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-479-41456 → 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/47941456, documented in the API reference.