WELL · 42-317-33390 · DISTRICT 8

Jennifer #1

Plugged

Martin County · Clem (Devonian) field  · Vertical

Jennifer #1 (API 42-317-33390) is a plugged well in Martin County, plugged May 17, 2002, last operated by Quay Valley Inc..

The RRC has issued one drilling permit (amended once), issued October 14, 1986, permitted to 11,600 ft.

It was permitted by Tri-Service Drilling CO. and has since transferred to Quay Valley Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Strawn, Mississippian, Devonian.

Its lease has reported 7.43K barrels of oil and 25 mcf of gas since January 1993, last reporting in July 2002.

Operator of record

Quay Valley Inc.

Permitted by Tri-Service Drilling Co.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Feb 3, 2006

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleQuay Valley Inc.
Production reportsQuay Valley, Inc.through Mar 2000
Latest permitTri-Service Drilling Co.Oct 14, 1986

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

11,600
total depth, ft
2
permits on file
Oct 14, 1986
last permit issued
Nov 24, 1986
completed
7.43K
cumulative oil, bbl
25
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 24, 1986
Shut in
—
Plugged
May 17, 2002

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
Jennifer O-10-30977Clem (Devonian)Quay Valley, Inc.17.43K25Jan 1993 – Jul 2002

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. 1Caprock Operating, Inc.Jan 1993 → Sep 1993
  2. 2Sahara Operating CompanyOct 1993 → Jun 1996
  3. 3Quay Valley, Inc.Jul 1996 → Mar 2000

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
321784-98DrillTri-Service Drilling Co.Oct 20, 1986Oct 14, 1986—11,600
321784-99DrillTri-Service Drilling Co.Oct 13, 1986Oct 14, 1986—11,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-30977————

Formation tops

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

FormationMD ftSubsea
Strawn10,456-7,620
Mississippian11,020-8,184
Devonian11,378-8,542

Perforations

Perforated and open-hole intervals.

FromToType
11,45411,474Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37534017.5370 S
9.6254,00812.25780 S
5.515,5188.751,050 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
00Dec 29, 1986Nov 26, 1986Yes
00Dec 20, 1986——

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) and the University Lands library. 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/31733390, documented in the API reference.