WELL · 42-365-34642 · DISTRICT 6

McNeese #3

Y

Panola County · Carthage (Glen Rose) field · Temp Abandoned  · Vertical

Mcneese #3 (API 42-365-34642) is a well in Panola County operated by Gary Production Company, completed June 13, 2001 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued March 16, 2001, permitted to 4,300 ft.

It was permitted by Essex Energy Of Texas Inc. and has since transferred to Gary Production Company on the wellbore schedule.

Completion filings report 3 formation tops, including Base Annona, Box Annona, Glen Rose.

No lease production has been reported under this well’s leases.

Operator of record

Gary Production Company

Permitted by Essex Energy of Texas Inc.; the EWA schedule now lists a different operator.

Carthage, TX · P-5 Y, filed Dec 4, 2025 · (903) 754-3115

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGary Production Company
Production reportsGary Production Companythrough Sep 2015
Latest permitEssex Energy of Texas Inc.Mar 16, 2001

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

4,300
total depth, ft
1
permits on file
Mar 16, 2001
last permit issued
Jun 13, 2001
completed
0
cumulative oil, bbl
12.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 13, 2001
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
McNeese G-6-188754Carthage (Glen Rose)Gary Production Company1012.4KJun 2001 – 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. 1Waterman Oil & Gas, Inc.Nov 2003 → Nov 2004
  2. 2Dorado Operating Inc.Mar 2006 → Aug 2006
  3. 3Gary Production CompanyOct 2014 → Sep 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
506564-99DrillEssex Energy of Texas Inc.Mar 16, 2001Mar 16, 2001Jun 6, 20014,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-188754————

Formation tops

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

FormationMD ftSubsea
Base Annona2,000-1,693
Box Annona2,000-1,693
Glen Rose3,269-2,962

Perforations

Perforated and open-hole intervals.

FromToType
3,9804,116Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,03811281 S
5.54,3317.875500 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, 2005Sep 6, 2005—
00Jun 28, 2002May 23, 2002Yes
00May 31, 2002——

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