WELL · 42-347-32186 · DISTRICT 6

Spivey #1

Plugged

Nacogdoches County · Naconiche Creek (Rod.-TP Cons.) field  · Vertical

Spivey #1 (API 42-347-32186) is a plugged well in Nacogdoches County, plugged August 18, 2016, last operated by Southwest Operating Inc.-Tyler.

The RRC has issued one drilling permit, issued December 27, 2005, permitted to 9,000 ft.

Completion filings report 5 formation tops, including Base Of Massive, B.O.M., James Lime, Pettit.

Its 2 leases have reported 2.17K barrels of oil and 292K mcf of gas since April 2006, last reporting in October 2021. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Southwest Operating Inc.-Tyler

Based in
Tyler, TX
P-5 status
Active – Extension (X)
P-5 last filed
Mar 4, 2026
Permits on file
63
Phone
(903) 597-4279

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSouthwest Operating Inc.-Tyler
Production reportsSouthwest Operating, Inc.-Tylerthrough Aug 2016
Latest permitSouthwest Operating, Inc.-TylerDec 27, 2005
9,000
total depth, ft
1
permits on file
Dec 27, 2005
last permit issued
Apr 5, 2006
completed
2.17K
cumulative oil, bbl
292K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2006 THROUGH Oct 2021

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 5, 2006
Shut in
—
Plugged
Aug 18, 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Spivey O-6-14715Naconiche Creek (Rod.-TP Cons.)Southwest Operating, Inc.-Tyler12.17K99.1KSep 2007 – Oct 2021
Spivey G-6-225274Naconiche Creek (Rod.-TP Cons.)Southwest Operating, Inc.-Tyler10193KApr 2006 – Apr 2008

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. 1Southwest Operating, Inc.-TylerMay 2006 → May 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
611250-99DrillSouthwest Operating, Inc.-TylerDec 19, 2005Dec 27, 2005Feb 27, 20069,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-225274————
—— O-6-14715————

Formation tops

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

FormationMD ftSubsea
Base of Massive6,345-5,864
B.O.M.6,345-5,864
James Lime6,835-6,354
Pettit7,100-6,619
Travis Peak7,650-7,169

Perforations

Perforated and open-hole intervals.

FromToType
7,7048,072Perforated
7,7048,077Perforated
8,6748,990Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,60411416 S
4.58,9957.875471 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 28, 2008Oct 9, 2007—
00Jan 8, 2008Jul 7, 2006Yes
00Dec 7, 2007——
00Mar 14, 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/34732186, documented in the API reference.