WELL · 42-227-36109 · DISTRICT 8

Jacy #1701

Plugged

Howard County · Spraberry (Trend Area) field  · Vertical

Jacy #1701 (API 42-227-36109) is a plugged well in Howard County, plugged June 23, 2011, last operated by Legacy Reserves Operating LP.

The RRC has issued one drilling permit (amended once), issued January 14, 2008, permitted to 10,800 ft.

It was permitted by Henry Petroleum LP and has since transferred to Legacy Reserves Operating LP on the wellbore schedule.

Completion filings report 3 formation tops, including T. Spraberry, T. Dean, T. Wolfcamp.

Its lease has reported 4.97K barrels of oil and 10.8K mcf of gas since September 2008, last reporting in October 2011.

Operator of record

Legacy Reserves Operating LP

Permitted by Henry Petroleum LP; the EWA schedule now lists a different operator.

Based in
Denver, CO
P-5 status
Inactive (I)
P-5 last filed
May 19, 2025
Permits on file
439
Phone
(720) 244-4898

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLegacy Reserves Operating LP
Production reportsCOG Operating LLCthrough Dec 2010
Latest permitHenry Petroleum LPJan 14, 2008

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

10,800
total depth, ft
2
permits on file
Jan 14, 2008
last permit issued
Dec 22, 2008
completed
4.97K
cumulative oil, bbl
10.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2008 THROUGH Oct 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 22, 2008
Shut in
—
Plugged
Jun 23, 2011

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Jacy O-10-39077Spraberry (Trend Area)Legacy Reserves Operating LP14.97K10.8KSep 2008 – Oct 2011

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.

  1. 1COG Operating LLCSep 2008 → Dec 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
652480-98DrillHenry Petroleum LPFeb 27, 2008Jan 14, 2008Apr 5, 200810,800
652480-99DrillHenry Petroleum LPJan 4, 2008Jan 14, 2008Apr 5, 200810,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-39077————

Formation tops

As filed on W-2/G-1. Subsea from 2,432 ft elevation.Download CSV →

FormationMD ftSubsea
T. Spraberry4,825-2,393
T. Dean6,175-3,743
T. Wolfcamp6,275-3,843

Perforations

Perforated and open-hole intervals.

FromToType
7,1807,950Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,570111,320 S
5.58,2507.875850 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Feb 19, 2009Jan 7, 2009Yes
00Feb 4, 2009——

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.

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/22736109, documented in the API reference.