TEXAS · WELLS · HEMPHILL COUNTY · HOLLAND C LEASE · API 42-211-32696 · DISTRICT 08
Holland C #5709P
Hemphill County · Buffalo Wallow (Granite Wash) field · Vertical
Holland C #5709P (API 42-211-32696) is a plugged well in Hemphill County, plugged March 28, 2018, last operated by Unit Petroleum Company.
The RRC has issued one drilling permit, issued February 10, 2003, permitted to 12,000 ft.
It was permitted by Patina Oil & Gas Corporation and has since transferred to Unit Petroleum Company on the wellbore schedule.
Completion filings report 2 formation tops, including Cleveland, Granite Wash.
Its lease has reported 6.16K barrels of oil and 457K mcf of gas since June 2003, with no volume in the three years through April 2026.
Operator of record
Permitted by Patina Oil & Gas Corporation; the EWA schedule now lists a different operator.
- Based in
- Tulsa, OK
- P-5 status
- Active (A)
- P-5 last filed
- Jan 13, 2025
- Permits on file
- 1,100
- Phone
- (918) 493-7700
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Unit Petroleum Company |
| Production reports | Unit Petroleum Companythrough Apr 2015 |
| Latest permit | Patina Oil & Gas CorporationFeb 10, 2003 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 12,000
- total depth, ft
- 1
- permits on file
- Feb 10, 2003
- last permit issued
- Jun 27, 2003
- completed
- 6.16K
- cumulative oil, bbl
- 457K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2003 THROUGH Apr 2015
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 27, 2003
- Shut in
- —
- Plugged
- Mar 28, 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 |
|---|---|---|---|---|---|---|
| Holland C G-14-197565 | Buffalo Wallow (Granite Wash) | Unit Petroleum Company | 1 | 6.16K | 457K | Jun 2003 – Apr 2015 |
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.
- 1Patina Oil & Gas CorporationJul 2003 → May 2005
- 2Noble Energy Production, Inc.Jun 2005 → Aug 2007
- 3Noble Energy IncSep 2007 → Aug 2012
- 4Unit Petroleum CompanySep 2012 → Apr 2015
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 528036-99 | Drill | Patina Oil & Gas Corporation | Feb 4, 2003 | Feb 10, 2003 | May 30, 2003 | 12,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jun 27, 2003 | Holland C G-14-197565 | Buffalo Wallow (Granite Wash) | Unit Petroleum Company | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,770 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| ClevelandCLEVELAND SS | 10,304 | -7,534 |
| Granite WashGRANITE WASH A-1 | 11,155 | -8,385 |
| Granite WashGRANITE WASH A | 11,193 | -8,423 |
| Granite WashGRANITE WASH B | 11,369 | -8,599 |
| Granite WashGRANITE WASH C | 11,682 | -8,912 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 11,207 | 11,330 | Perforated |
| 11,485 | 11,620 | Perforated |
| 11,746 | 11,814 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,209 | 11 | 650 S |
| 4.5 | 11,945 | 7.875 | 500 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 | Nov 24, 2003 | Oct 13, 2003 | Yes |
| 00 | Nov 13, 2003 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Oct 23, 2006. Gamma ray, 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 |
|---|---|---|---|---|
| ResistivityHIGH DEFINITION INDUCTION GAMMA RAYSpans Cleveland, Granite Wash | TIFF | 1,206 to 11,960 | Oct 23, 2006run Jun 14, 2003 | — |
"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-211-32696 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-211-32696 → 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/21132696, documented in the API reference.