WELL · 42-297-34716 · DISTRICT 2

McNeill North #3

Y

Live Oak County · C. A. Winn (Yegua 5320) field · Shut IN  · Vertical

Mcneill North #3 (API 42-297-34716) is a well in Live Oak County operated by Double Play Oil & Gas Inc, completed February 26, 2007 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued January 24, 2007, permitted to 6,024 ft.

Completion filings report 4 formation tops, including Het, Hett, Pettus, Yegua.

Its 2 leases have reported 132K barrels of oil and 204K mcf of gas since February 2007, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Double Play Oil & Gas Inc

Portland, TX · P-5 Y, filed Oct 4, 2025 · 260 permits on file · (361) 765-5399

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDouble Play Oil & Gas Inc
Production reportsDouble Play Oil & Gas, Incthrough Mar 2024
Latest permitDouble Play Oil & Gas, IncJan 24, 2007
6,024
total depth, ft
2
permits on file
Jan 24, 2007
last permit issued
Feb 26, 2007
completed
132K
cumulative oil, bbl
204K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 26, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
McNeill North O-2-9161C. A. Winn, NE. (Hockley 4300)Double Play Oil & Gas, Inc1117K147KFeb 2007 – Jul 2026
McNeill North O-2-9162C. A. Winn (Yegua 5320)Double Play Oil & Gas, Inc115K57.3KFeb 2007 – Jul 2026

Oil, barrels lease total

Last 12 months 0 · prior 12 0

01202420252026

Chain of custody

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

  1. 1Double Play Oil & Gas, IncFeb 2007 → Mar 2024
  2. 2Sue-Ann Operating, L.C.Apr 2018 → Oct 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
632249-98DrillDouble Play Oil & Gas, IncApr 26, 2007Jan 24, 2007Jan 31, 20076,024
632249-99DrillDouble Play Oil & Gas, IncJan 22, 2007Jan 24, 2007—6,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-9161————
—— O-2-9162————

Formation tops

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

FormationMD ftSubsea
Het2,230-1,977
Hett2,230-1,977
Pettus4,970-4,717
Yegua5,170-4,917

Perforations

Perforated and open-hole intervals.

FromToType
4,4004,411Perforated
5,1755,216Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.55,2657.8751,035 S
8.875———

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
00Feb 8, 2008May 24, 2007Yes
00Dec 10, 2007——

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