WELL · 42-261-31548 · DISTRICT 4
Crocker Unit #1
Kenedy County · Canelo (I-08 S) field · Producing · Vertical
Crocker Unit #1 (API 42-261-31548) is a well in Kenedy County operated by Dewbre Petroleum Corporation, completed May 16, 2011 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued November 23, 2010, permitted to 10,500 ft.
Completion filings report one formation top, including I-08 Sand.
No lease production has been reported under this well’s leases.
Operator of record
Corpus Christ, TX · P-5 Y, filed Sep 4, 2025 · 366 permits on file · (361) 888-7978
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Dewbre Petroleum Corporation |
| Production reports | Dewbre Petroleum Corporationthrough Apr 2026 |
| Latest permit | Dewbre Petroleum CorporationNov 23, 2010 |
- 10,500
- total depth, ft
- 1
- permits on file
- Nov 23, 2010
- last permit issued
- May 16, 2011
- completed
- 0
- cumulative oil, bbl
- 1.85M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 2011 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- May 16, 2011
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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 |
|---|---|---|---|---|---|---|
| Crocker Unit G-4-261223 | Canelo (I-08, S) | Dewbre Petroleum Corporation | 1 | 0 | 1.85M | May 2011 – Jul 2026 |
Gas, mcf lease total
Last 12 months 33,510 · prior 12 64,052(-48%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Dewbre Petroleum CorporationMay 2011 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 705757-99 | Drill | Dewbre Petroleum Corporation | Nov 19, 2010 | Nov 23, 2010 | Dec 27, 2010 | 10,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-261223 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 41 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| I-08 Sand | 9,632 | -9,591 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,635 | 9,655 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,525 | 12.25 | 222 S |
| 4.5 | 9,889 | 7.875 | 320 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 | Nov 3, 2011 | May 25, 2011 | 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-261-31548 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-261-31548 → 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/26131548, documented in the API reference.