WELL · 42-227-37880 · DISTRICT 8
Crown Exploration Bigby #1
Howard County · Spraberry (Trend Area) field · Injection · Vertical
Crown Exploration Bigby #1 (API 42-227-37880) is a well in Howard County operated by Highpeak Energy Holdings LLC, completed March 9, 2024 and listed as injection on the RRC schedule.
The RRC has issued one drilling permit, issued March 6, 2014, permitted to 7,700 ft.
It was permitted by Western Chief Operating, L.L.C. and has since transferred to Highpeak Energy Holdings LLC on the wellbore schedule.
Completion filings report 19 formation tops, including Yates, Seven Rivers, Glorieta, San Andres.
Its lease has reported 15.6K barrels of oil since August 2014, last reporting in July 2026.
It holds an active disposal or injection permit, with 4.69M barrels injected in the 12 months reported through January 2026.
Operator of record
Permitted by Western Chief Operating, L.L.C.; the EWA schedule now lists a different operator.
Fort Worth, TX · P-5 Y, filed Sep 4, 2025 · 896 permits on file · (432) 894-2640
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Highpeak Energy Holdings LLC |
| Production reports | Highpeak Energy Holdings, LLCthrough Aug 2020 |
| Latest permit | Western Chief Operating, L.L.C.Mar 6, 2014 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 7,700
- total depth, ft
- 1
- permits on file
- Mar 6, 2014
- last permit issued
- Mar 9, 2024
- completed
- 15.6K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2014 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Mar 9, 2024
- 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 |
|---|---|---|---|---|---|---|
| Crown Exploration Bigby O-10-45687 | Spraberry (Trend Area) | Highpeak Energy Holdings, LLC | 1 | 15.6K | 0 | Aug 2014 – 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.
- 1Western Chief Operating, L.L.C.Aug 2014 → Jun 2018
- 2Highpeak Energy Holdings, LLCJul 2018 → Aug 2020
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 779666-99 | Drill | Western Chief Operating, L.L.C. | Feb 12, 2014 | Mar 6, 2014 | Mar 11, 2014 | 7,700 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-10-45687 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,440 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Yates | 1,250 | 1,190 |
| Seven Rivers | 1,300 | 1,140 |
| Glorieta | 2,400 | 40 |
| GlorietaGLORIETTA | 2,400 | 40 |
| San AndresSAN ANDRES - HIGH FLOWS, H2S, CO | 2,500 | -60 |
| San AndresSAN ANDRES - HIGH FLOWS,H2S,CORR | 2,500 | -60 |
| Coleman Junction | 3,400 | -960 |
| Clear ForkCLEARFORK - SEVERE WATER FLOWS | 4,510 | -2,070 |
| Spraberry | 4,851 | -2,411 |
| Leonard | 5,871 | -3,431 |
| Dean | 6,101 | -3,661 |
| Wolfcamp | 6,288 | -3,848 |
| Atoka | — | — |
| Canyon | — | — |
| Cisco | — | — |
| Coleman Junction | — | — |
| Ellenburger | — | — |
| Fusselman | — | — |
| Glorieta | — | — |
| MississippianMISSISSIPPIAN-FUSSELMAN | — | — |
| Pennsylvanian | — | — |
| Seven Rivers | — | — |
| Silurian (undifferentiated)SILURIAN-DEVONIAN | — | — |
| Strawn | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,570 | 3,225 | Perforated |
| 5,392 | 5,412 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 416 | 17.5 | 375 S |
| 8.625 | 2,709 | 11 | 660 S |
| 7 | 4,003 | 7.875 | 640 S |
| 4.5 | 7,077 | 6.25 | 400 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 3, 2025 | Nov 7, 2024 | — |
| 00 | Aug 17, 2021 | Aug 4, 2021 | — |
| 00 | Jun 23, 2021 | Jun 9, 2021 | — |
| 00 | Feb 2, 2015 | Sep 25, 2014 | 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-227-37880 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-227-37880 → 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.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 4.69M
- bbl, last 12 reported months
- 6.6M
- bbl, all reported
- Jan 2026
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000126337 | W-14 Disposal | Active | 30,000 | 1,200 | 2,560–3,450 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 4,687,755 · prior 12 1,910,802(+145%)
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/22737880, documented in the API reference.