WELL · 42-285-00608 · DISTRICT 2

Traylor A.V. #8

Plugged

Lavaca County · Provident City (Yegua -M-1) field  · Vertical

Traylor A.V. #8 (API 42-285-00608) is a plugged well in Lavaca County, plugged September 13, 2005, last operated by Neg Operating LLC.

The RRC has issued 2 drilling permits between 1985 and 1988, permitted to 12,448 ft.

It was permitted by Shell Western E&P Inc. and has since transferred to Neg Operating LLC on the wellbore schedule.

Completion filings report 5 formation tops, including Vicksburg, Jackson, Yegua, Cook Mountain.

Operator of record

Neg Operating LLC

Permitted by Shell Western E&P Inc.; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Y, filed Sep 11, 2015 · 238 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNeg Operating LLC
Production reportsShana Petroleum Companythrough Dec 1999
Latest permitShell Western E&P Inc.Apr 25, 1988

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

12,448
total depth, ft
2
permits on file
Apr 25, 1988
last permit issued
May 13, 1988
completed
0
cumulative oil, bbl
73.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2005

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 13, 1988
Shut in
—
Plugged
Sep 13, 2005

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
Traylor, A.V. G-2-127716Provident City (Yegua -M-1)Neg Operating LLC1073.7KJan 1993 – Sep 2005

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. 1Shell Western E&P Inc.Nov 1994 → Jan 1998
  2. 2Shana Petroleum CompanyOct 1999 → Dec 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
345565-99RecompletionShell Western E&P Inc.Apr 22, 1988Apr 25, 1988—12,448
291982-99RecompletionShell Western E&P Inc.Dec 6, 1985Dec 6, 1985—12,448

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-127716————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Vicksburg4,000
Jackson4,282
Yegua5,347
Yegua5,348
Cook Mountain6,542
Wilcox8,475

Perforations

Perforated and open-hole intervals.

FromToType
5,8425,852Perforated
9,4419,364Perforated
12,42312,448Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,83117.51,630 S
9.62510,44012.25600 S
5.514,4266.75450 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
00Jul 18, 1988May 27, 1988Yes
00Jul 14, 1988——
00May 13, 1986Mar 27, 1986Yes
00May 8, 1986——
00Jan 12, 1984Jun 25, 1970—
00Jan 12, 1984——

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