WELL · 42-499-31076 · DISTRICT 6

Nolan Edward Water Flood Unit #31

Plugged

Wood County · Nolan Edward field  · Vertical

Nolan Edward Water Flood Unit #31 (API 42-499-31076) is a plugged well in Wood County, plugged May 3, 1993, last operated by Meshell Martha Oil Company.

The RRC has issued one drilling permit, issued March 17, 1982, permitted to 5,000 ft.

It was permitted by Richey Operating, Inc. and has since transferred to Meshell Martha Oil Company on the wellbore schedule.

Completion filings report 3 formation tops, including Nacatoch, Pecan Gap, Austin Chalk.

Operator of record

Meshell Martha Oil Company

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

Kilgore, TX · P-5 Y, filed Dec 3, 1993

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMeshell Martha Oil Company
Production reportsnone
Latest permitRichey Operating, Inc.Mar 17, 1982

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

5,000
total depth, ft
1
permits on file
Mar 17, 1982
last permit issued
Jul 10, 1982
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 10, 1982
Shut in
—
Plugged
May 3, 1993

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 7 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Nolan Edward Water Flood Unit O-6-2930Nolan EdwardMeshell, Martha Oil Company700Jan 1993 – Aug 2003

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
153746-99DrillRichey Operating, Inc.Mar 17, 1982Mar 17, 1982—5,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-2930————

Formation tops

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

FormationMD ftSubsea
Nacatoch1,986-1,585
Pecan Gap2,784-2,383
Austin Chalk4,398-3,997

Perforations

Perforated and open-hole intervals.

FromToType
4,6694,677Perforated
4,6914,696Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62516712.25120 S
2.3754,696——
4.54,9827.8751,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 19, 1984Dec 3, 1984—
00Jan 12, 1984May 9, 1983—

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
4.68K
bbl, all reported
Mar 1993
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000053944H-1 InjectionPlugged May 20, 1993004,669–0

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 325(-100%)

05010015019921993

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