WELL · 42-001-31314 · DISTRICT 6

Wylie SO A #2

Plugged

Anderson County · Carol Jean (James Lime) field  · Vertical

Wylie SO A #2 (API 42-001-31314) is a plugged well in Anderson County, plugged September 23, 2015, last operated by O Benco Inc..

The RRC has issued one drilling permit, issued December 18, 1981, permitted to 10,600 ft.

It was permitted by Mole Operating CO., Inc. and has since transferred to O Benco Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Woodbine, Paluxy, Rodessa, James Lime.

Its lease has reported 41K barrels of oil and 592K mcf of gas since January 1993, last reporting in November 2015.

Operator of record

O Benco Inc.

Permitted by Mole Operating Co., Inc.; the EWA schedule now lists a different operator.

Shreveport, LA · P-5 Y, filed Mar 11, 2022 · 374 permits on file · (318) 865-8568

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleO Benco Inc.
Production reportsO'Benco, Inc.through Feb 2013
Latest permitMole Operating Co., Inc.Dec 18, 1981

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

10,600
total depth, ft
1
permits on file
Dec 18, 1981
last permit issued
Feb 10, 1982
completed
41K
cumulative oil, bbl
592K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 10, 1982
Shut in
—
Plugged
Sep 23, 2015

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
Wylie, SO "A" O-6-11911Carol Jean (James Lime)O'Benco, Inc.141K592KJan 1993 – Nov 2015

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. 1Big Run Production CompanyJan 1993 → Jun 1999
  2. 2O'Benco, Inc.Jul 1999 → Feb 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
144833-99DrillMole Operating Co., Inc.Dec 18, 1981Dec 18, 1981—10,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-11911————

Formation tops

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

FormationMD ftSubsea
Woodbine5,010-4,546
Paluxy7,460-6,996
Rodessa9,680-9,216
James LimeJAMES10,050-9,586

Perforations

Perforated and open-hole intervals.

FromToType
10,06510,071Perforated
10,08810,098Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,76011400 S
2.37510,060——
4.510,4617.875600 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
00Apr 3, 1986Feb 7, 1985—
00Apr 1, 1986——
00Apr 4, 1985Feb 7, 1985—
00Apr 2, 1985——
00Jan 12, 1984Feb 12, 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/00131314, documented in the API reference.