WELL · 42-423-31192 · DISTRICT 6

Epperson #1

N

Smith County · Lane Chapel W. (Paluxy B) field  · Vertical

Epperson #1 (API 42-423-31192) is a well in Smith County operated by Palrich Oil Corporation, completed May 11, 1989.

The RRC has issued one drilling permit, issued April 6, 1989, permitted to 10,000 ft.

Completion filings report 5 formation tops, including Austin Chalk, Woodbine, Maness, Kiamichi.

Its 2 leases have reported 980K barrels of oil and 284K mcf of gas since January 1993, last reporting in July 2026. The leases carry 15 wells, so these are lease totals, not this well alone.

Operator of record

Palrich Oil Corporation

Abilene, TX · P-5 Y, filed Jun 4, 2004 · 81 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePalrich Oil Corporation
Production reportsAtlantis Oil Company, Inc.through Apr 2026
Latest permitPalrich Oil CorporationApr 6, 1989

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

10,000
total depth, ft
1
permits on file
Apr 6, 1989
last permit issued
May 11, 1989
completed
980K
cumulative oil, bbl
284K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 11, 1989
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 2 leases this well is completed on; they carry 15 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Lane Chapel, W. (Paluxy B) Unit O-6-13815Lane Chapel, W. (Paluxy B)Atlantis Oil Company, Inc.13924K77.6KJun 1998 – Jul 2026
Epperson O-6-12544Lane Chapel, W. (Paluxy B)Palrich Oil Corporation256K206KJan 1993 – Aug 1998

Oil, barrels lease total

Last 12 months 8,660 · prior 12 9,445(-8%)

05001K1.5K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Palrich Oil CorporationJan 1993 → Apr 2004
  2. 2Atlantis Oil Company, Inc.May 2004 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
357856-99DrillPalrich Oil CorporationApr 6, 1989Apr 6, 1989—10,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-12544————
—— O-6-13815————

Formation tops

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

FormationMD ftSubsea
Austin Chalk4,248-3,798
Woodbine4,590-4,140
ManessMANESS SHALE5,208-4,758
Kiamichi6,564-6,114
Paluxy6,809-6,359

Perforations

Perforated and open-hole intervals.

FromToType
6,8716,883Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,43311470 S
4.57,1847.875800 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
00Jun 2, 1998May 19, 1989Yes
00Aug 3, 1989May 19, 1989Yes
00Jul 26, 1989——

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