WELL · 42-189-30511 · DISTRICT 8
Heard 4 #1
Hale County · Wildcat field · Vertical
Heard 4 #1 (API 42-189-30511) is a plugged well in Hale County, plugged March 27, 2015, last operated by Anschutz Exploration Corporation.
The RRC has issued one drilling permit, issued October 26, 2013, permitted to 10,500 ft.
It was permitted by Laredo Petroleum, Inc. and has since transferred to Anschutz Exploration Corporation on the wellbore schedule.
Completion filings report 4 formation tops, including L Wolfcamp, Cisco, Canyon, Strawn.
Operator of record
Anschutz Exploration Corporation
Permitted by Laredo Petroleum, Inc.; the EWA schedule now lists a different operator.
Denver, CO · P-5 Y, filed Mar 4, 2016 · 56 permits on file · (888) 696-1300
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Anschutz Exploration Corporation |
| Production reports | none |
| Latest permit | Laredo Petroleum, Inc.Oct 26, 2013 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 10,500
- total depth, ft
- 1
- permits on file
- Oct 26, 2013
- last permit issued
- Jul 2, 2014
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2014 THROUGH Jun 2015
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jul 2, 2014
- Shut in
- —
- Plugged
- Mar 27, 2015
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 |
|---|---|---|---|---|---|---|
| Heard 4 O-11-70232 | Wildcat | Anschutz Exploration Corporation | 1 | 0 | 0 | Jul 2014 – Jun 2015 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 771719-99 | Drill | Laredo Petroleum, Inc. | Oct 14, 2013 | Oct 26, 2013 | Dec 12, 2013 | 10,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-11-70232 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 3,321 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,910 | 7,979 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 17.5 | 561 | 13.375 | 610 S |
| 12.25 | 3,236 | 9.625 | 873 S |
| 8.75 | 10,281 | 7 | 963 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 | Oct 23, 2014 | Jul 16, 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-189-30511 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-189-30511 → 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/18930511, documented in the API reference.