WELL · 42-065-31187 · DISTRICT 10

Sanford -B- #2

Y

Carson County · Panhandle Carson County Field field · Shut IN  · Vertical

Sanford -B- #2 (API 42-065-31187) is a well in Carson County operated by Lera, completed May 19, 1982 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued May 12, 1982, permitted to 3,150 ft.

It was permitted by Jay-Dee Producing Company and has since transferred to Lera on the wellbore schedule.

Its lease has reported 3.01K barrels of oil and 136K mcf of gas since January 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Lera

Permitted by Jay-Dee Producing Company; the EWA schedule now lists a different operator.

Borger, TX · P-5 Y, filed Jun 4, 2026 · 34 permits on file · (806) 886-0998

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLera
Production reportsPG-M International Operating,llcthrough Jun 2016
Latest permitJay-Dee Producing CompanyMay 12, 1982

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

3,150
total depth, ft
1
permits on file
May 12, 1982
last permit issued
May 19, 1982
completed
3.01K
cumulative oil, bbl
136K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 19, 1982
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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sanford -B- O-14-2394Panhandle Carson County FieldLera23.01K136KJan 1993 – 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. 1Davis, D. D. Estate OFJan 1993 → May 1998
  2. 2Tess Oil CompanyJun 1998 → Dec 2003
  3. 3Jaco Oil & GasJan 2004 → Sep 2005
  4. 4LeraMay 2007 → Apr 2009
  5. 5Rimrock Gas CompanyMar 2008 → May 2008
  6. 6Sniper Oil & Gas, Inc.Jun 2009 → Jan 2013
  7. 7Petrolia Group, L.L.C.Apr 2013 → Nov 2013
  8. 8PG-M International Operating,llcApr 2014 → Jun 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
160773-99DrillJay-Dee Producing CompanyMay 12, 1982May 12, 1982—3,150

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-2394————

Perforations

Perforated and open-hole intervals.

FromToType
3,0802,900Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62537512.25250 S
2.3753,050——
5.53,1407.875150 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
00Jan 12, 1984Jul 30, 1982—

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