WELL · 42-297-34042 · DISTRICT 2
Block 86 Unit #4
Live Oak County · Clayton (Block 86 SD) field · Vertical
Block 86 Unit #4 (API 42-297-34042) is a well in Live Oak County operated by Parker & Parsley Development L.P, completed November 22, 1992.
The RRC has issued 3 drilling permits (amended once) between 1992 and 2011, permitted to 8,600 ft.
It was permitted by Vistatex Energy LLC and has since transferred to Parker & Parsley Development L.P on the wellbore schedule.
Completion filings report 4 formation tops, including Clayton Block 75 Sd, Block 85 Sd, Block 86 Sd, Previously Submitted.
No lease production has been reported under this well’s leases.
Operator of record
Parker & Parsley Development L.P
Permitted by Vistatex Energy LLC; the EWA schedule now lists a different operator.
Midland, TX · P-5 Y, filed Jun 20, 2003 · 1,422 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Parker & Parsley Development L.P |
| Production reports | Calpine Natural Gas L.P.through Jun 2004 |
| Latest permit | Vistatex Energy LLCNov 9, 2011 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,600
- total depth, ft
- 4
- permits on file
- Nov 9, 2011
- last permit issued
- Nov 22, 1992
- completed
- 0
- cumulative oil, bbl
- 2.28M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 22, 1992
- Shut in
- —
- Plugged
- —
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 4 leases this well is completed on; they carry 4 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Block 86 Unit G-2-144903 | Clayton (Block 85 SD) | Hedrick Production Inc. | 1 | 0 | 1.74M | Jan 1993 – Jul 2026 |
| Block 86 Unit G-2-195692 | Clayton (Block 75 SD) | Hedrick Production Inc. | 1 | 0 | 55.4K | Dec 2001 – Jul 2026 |
| Clayton Block 86 Unit G-2-263367 | Clayton (Block 72 Sd.) | Hedrick Production Inc. | 1 | 0 | 0 | Nov 2011 – Jul 2026 |
| Block 86 Unit G-2-144230 | Clayton (Block 86 SD) | Parker & Parsley Development L.P | 1 | 0 | 479K | Jan 1993 – Mar 1997 |
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.
- 1Parker & Parsley Development Co.Jan 1993 → Feb 1995
- 2Parker & Parsley Development L.PMar 1995 → Aug 1997
- 3Pioneer Natural Res. USA, Inc.Sep 1997 → Nov 1997
- 4Sheridan Energy,inc.Dec 1997 → Feb 2000
- 5Calpine Natural Gas CompanyMar 2000 → Dec 2001
- 6Calpine Natural Gas L.P.Dec 2001 → Jun 2004
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 727093-99 | Recompletion | Vistatex Energy LLC | Oct 26, 2011 | Nov 9, 2011 | Nov 14, 2011 | 8,500 |
| 514068-99 | Recompletion | Calpine Natural Gas Company | Oct 1, 2001 | Oct 2, 2001 | Dec 3, 2001 | 8,290 |
| 403966-98 | Drill | Parker & Parsley Development Co. | Nov 18, 1992 | Sep 28, 1992 | — | 8,600 |
| 403966-99 | Drill | Parker & Parsley Development Co. | Sep 28, 1992 | Sep 28, 1992 | Oct 3, 1992 | 8,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-144230 | — | — | — | — |
| — | — G-2-144903 | — | — | — | — |
| — | — G-2-195692 | — | — | — | — |
| — | — G-2-263367 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 378 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Clayton Block 75 SD | 7,564 | -7,186 |
| Block 85 SD | 7,812 | -7,434 |
| Block 86 SD | 8,330 | -7,952 |
| Previously Submitted | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,564 | 7,592 | Perforated |
| 7,624 | 7,642 | Perforated |
| 7,812 | 7,820 | Perforated |
| 8,330 | 8,386 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 2,072 | 12.25 | 780 S |
| 9.625 | 2,072 | 14.75 | 785 S |
| 9.5 | 8,500 | 8.5 | 1,135 S |
| 5.5 | 8,500 | 8.5 | 1,135 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 9, 2012 | Nov 28, 2011 | — |
| 00 | Jan 27, 2005 | Jun 17, 2004 | — |
| 00 | Nov 29, 2004 | May 6, 2004 | — |
| 00 | Dec 10, 2003 | Nov 7, 2002 | — |
| 00 | Jul 30, 2003 | — | — |
| 00 | Jun 20, 1997 | Mar 24, 1997 | — |
| 00 | Apr 1, 1994 | Oct 25, 1993 | — |
| 00 | Jun 11, 1993 | Dec 16, 1992 | — |
| 00 | Apr 30, 1993 | — | — |
| 00 | Apr 13, 1993 | Dec 16, 1992 | Yes |
| 00 | Mar 11, 1993 | — | — |
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-297-34042 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-297-34042 → 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/29734042, documented in the API reference.