TEXAS · WELLS · GLASSCOCK COUNTY · DRIVER LEASE · API 42-173-33775 · DISTRICT 7B
Driver #1
Glasscock County · Garden City S. (Wolfcamp) field · Producing · Vertical
Driver #1 (API 42-173-33775) is a well in Glasscock County operated by Crescent Energy Operating LLC, completed September 20, 2010 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit (amended once), issued September 1, 2010, permitted to 9,900 ft.
It was permitted by Laredo Petroleum, Inc. and has since transferred to Crescent Energy Operating LLC on the wellbore schedule.
Completion filings report 2 formation tops, including Spraberry, Wolfcamp.
Its lease has reported 76K barrels of oil and 485K mcf of gas since September 2010, last reporting volume in February 2026. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Laredo Petroleum, Inc.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Aug 28, 2025
- Permits on file
- 54
- Phone
- (713) 337-4600
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Crescent Energy Operating LLC |
| Production reports | Crescent Energy Operating, LLCthrough Feb 2026 |
| Latest permit | Laredo Petroleum, Inc.Sep 1, 2010 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,900
- total depth, ft
- 2
- permits on file
- Sep 1, 2010
- last permit issued
- Sep 20, 2010
- completed
- 76K
- cumulative oil, bbl
- 485K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2010 THROUGH Feb 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Sep 20, 2010
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (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; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Driver O-10-41077 | Garden City, S. (Wolfcamp) | Crescent Energy Operating, LLC | 2 | 76K | 485K | Sep 2010 – Feb 2026 |
Gas, mcf lease total
Last 12 months 17,233 · prior 12 24,161(-29%)
Oil, barrels lease total
Last 12 months 1,389 · prior 12 2,409(-42%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Laredo Petroleum, Inc.Oct 2010 → Jan 2023
- 2Vital Energy, Inc.Feb 2023 → Dec 2025
- 3Crescent Energy Operating, LLCJan 2026 → Feb 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 701494-98 | Drill | Laredo Petroleum, Inc. | Oct 19, 2010 | Sep 1, 2010 | — | 10,080 |
| 701494-99 | Drill | Laredo Petroleum, Inc. | Aug 30, 2010 | Sep 1, 2010 | Sep 20, 2010 | 10,080 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Sep 20, 2010 | Driver O-10-41077 | Garden City S. (Wolfcamp) | Crescent Energy Operating LLC | Producing | 9,900 |
Formation tops
As filed on W-2/G-1. Subsea from 2,718 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,644 | 9,723 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 523 | 17.5 | 300 S |
| 8.625 | 3,045 | 11 | 765 S |
| 5.5 | 9,900 | 7.875 | 895 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 23, 2012 | Feb 2, 2011 | Yes |
Well logs
2 logs loaded from the RRC's log index, the latest received Nov 18, 2013. 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 |
|---|---|---|---|---|
| NEUTRON/DENSITY POROSITYSpans Spraberry, Wolfcamp | TIFF | 100 to 9,902 | Nov 18, 2013run Oct 1, 2010 | 4.74 |
| RESISTIVITYSpans Spraberry, Wolfcamp | TIFF | 3,044 to 9,902 | Nov 18, 2013run Oct 1, 2010 | 4.11 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-173-33775 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-173-33775 → 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/17333775, documented in the API reference.