WELL · 42-347-31013 · DISTRICT 6

Mast A. T. #10

Plugged

Nacogdoches County · Nacogdoches field  · Vertical

Mast A. T. #10 (API 42-347-31013) is a plugged well in Nacogdoches County, plugged October 27, 2016, last operated by Arencia Oil CO. Inc..

The RRC has issued one drilling permit, issued March 31, 1983, permitted to 1,000 ft.

It was permitted by Moss Creek Petroleum, Inc. and has since transferred to Arencia Oil CO. Inc. on the wellbore schedule.

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

Operator of record

Arencia Oil Co. Inc.

Permitted by Moss Creek Petroleum, Inc.; the EWA schedule now lists a different operator.

Nacogdoches, TX · P-5 Y, filed Jul 8, 2016

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleArencia Oil Co. Inc.
Production reportsArencia Oil Co., Inc.through Jun 2003
Latest permitMoss Creek Petroleum, Inc.Mar 31, 1983

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

1,000
total depth, ft
1
permits on file
Mar 31, 1983
last permit issued
Apr 8, 1983
completed
152
cumulative oil, bbl
125
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 8, 1983
Shut in
—
Plugged
Oct 27, 2016

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Mast, A. T. O-6-10857NacogdochesArencia Oil Co., Inc.41152125Jan 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. 1Arencia Oil CompanyJan 1993 → May 1996
  2. 2Arencia Oil Co., Inc.Jun 1996 → Feb 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
192897-99DrillMoss Creek Petroleum, Inc.Mar 31, 1983Mar 31, 1983—1,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-10857————

Perforations

Perforated and open-hole intervals.

FromToType
563608Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
2.375564——
4.56756.550 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, 1984May 16, 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
0
bbl, all reported
Mar 1995
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000052212H-1 InjectionPlugged Oct 27, 201600563–0

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

Last 12 months 0 · prior 12 0

0119941995

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