WELL · 42-227-38494 · DISTRICT 8
Gratis 32 #1HB
Howard County · Spraberry (Trend Area) field · Horizontal
Gratis 32 #1HB (API 42-227-38494) is a plugged horizontal well in Howard County, plugged September 19, 2018, last operated by Crownquest Operating LLC.
The RRC has issued one drilling permit (amended once), issued March 3, 2015, permitted to 9,600 ft.
Completion filings report 10 formation tops, including Atoka, Canyon, Ellenburger, Fusselman.
Operator of record
- Based in
- Midland, TX
- P-5 status
- Active (A)
- P-5 last filed
- Aug 25, 2025
- Permits on file
- 3,231
- Phone
- (432) 818-0300
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Crownquest Operating LLC |
| Production reports | none |
| Latest permit | Crownquest Operating, LLCMar 3, 2015 |
- 9,600
- total depth, ft
- 2
- permits on file
- Mar 3, 2015
- last permit issued
- Nov 2, 2015
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 2015 THROUGH Apr 2019
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 2, 2015
- Shut in
- —
- Plugged
- Sep 19, 2018
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 |
|---|---|---|---|---|---|---|
| Gratis '32' O-10-47560 | Spraberry (Trend Area) | Crownquest Operating, LLC | 1 | 0 | 0 | Nov 2015 – Apr 2019 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 804189-98 | Drill | Crownquest Operating, LLC | Aug 6, 2015 | Mar 3, 2015 | Oct 15, 2015 | 9,600 |
| 804189-99 | Drill | Crownquest Operating, LLC | Feb 26, 2015 | Mar 3, 2015 | Oct 15, 2015 | 9,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-10-47560 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,559 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Atoka | — | — |
| Canyon | — | — |
| Ellenburger | — | — |
| Fusselman | — | — |
| MississippianMISSISSIPPIAN-FUSSELMAN | — | — |
| Pennsylvanian | — | — |
| Seven Rivers | — | — |
| Silurian (undifferentiated)SILURIAN-DEVONIAN | — | — |
| Strawn | — | — |
| Yates | — | — |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 300 | 17.5 | 350 S |
| 9.625 | 7,895 | 12.25 | 1,000 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 | May 11, 2016 | Feb 5, 2016 | 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-38494 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-227-38494 → 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/22738494, documented in the API reference.