WELL · 42-429-36421 · DISTRICT 7

Pilgrim #2

Y

Stephens County · Stephens County Regular (Gas) field · Shut IN  · Vertical

Pilgrim #2 (API 42-429-36421) is a well in Stephens County operated by Ray Herring Operating CO. LLC, completed February 27, 2009 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued April 18, 2008, permitted to 4,400 ft.

It was permitted by Herring, Ray and has since transferred to Ray Herring Operating CO. LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Caddo, Marble Falsl.

No lease production has been reported under this well’s leases.

Operator of record

Ray Herring Operating Co. LLC

Permitted by Herring, Ray; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Dec 4, 2025 · 8 permits on file · (940) 550-8988

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRay Herring Operating Co. LLC
Production reportsRay Herring Operating Co., LLCthrough Apr 2020
Latest permitHerring, RayApr 18, 2008

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

4,400
total depth, ft
1
permits on file
Apr 18, 2008
last permit issued
Feb 27, 2009
completed
0
cumulative oil, bbl
4.43K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 27, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Pilgrim G-8-247145Stephens County Regular (Gas)Ray Herring Operating Co., LLC104.43KFeb 2009 – Jul 2026

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. 1Herring, RayFeb 2009 → Jun 2014
  2. 2Ray Herring EstateJul 2014 → Apr 2015
  3. 3Ray Herring Operating Co., LLCDec 2016 → Apr 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
659047-99DrillHerring, RayApr 7, 2008Apr 18, 2008Apr 18, 20084,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-247145————

Formation tops

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

FormationMD ftSubsea
Caddo3,220-1,864
Caddo3,230-1,874
Marble Falsl3,800-2,444

Perforations

Perforated and open-hole intervals.

FromToType
2,1082,112Perforated
3,6773,685Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62526212.25185 S
7.87526212.25185 S
4.52,2287.875150 S
4.53,9207.875170 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
00Sep 8, 2015Aug 14, 2015—
00Jun 13, 2009Apr 17, 2009Yes
00May 20, 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/42936421, documented in the API reference.