WELL · 42-169-32945 · DISTRICT 8

Knox Estate A #1

Plugged

Garza County · Tufbow (Strawn) field  · Vertical

Knox Estate A #1 (API 42-169-32945) is a plugged well in Garza County, plugged June 14, 2000, last operated by Latigo Pipe & Equipment Inc..

The RRC has issued one drilling permit, issued October 12, 1989, permitted to 8,000 ft.

It was permitted by Samedan Oil Corporation and has since transferred to Latigo Pipe & Equipment Inc. on the wellbore schedule.

Completion filings report 6 formation tops, including San Andres, Glorieta, Wolfcamp, Strawn.

Its lease has reported 14.8K barrels of oil and 3.53K mcf of gas since January 1993, last reporting in September 2000.

Operator of record

Latigo Pipe & Equipment Inc.

Permitted by Samedan Oil Corporation; the EWA schedule now lists a different operator.

Blackwell, TX · P-5 Y, filed Nov 9, 2001

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLatigo Pipe & Equipment Inc.
Production reportsTepee Petroleum Co., Inc.through Apr 2000
Latest permitSamedan Oil CorporationOct 12, 1989

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

8,000
total depth, ft
1
permits on file
Oct 12, 1989
last permit issued
Jan 29, 1990
completed
14.8K
cumulative oil, bbl
3.53K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2000

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 29, 1990
Shut in
—
Plugged
Jun 14, 2000

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
Knox Estate "A" O-11-66476Tufbow (Strawn)Latigo Pipe & Equipment, Inc.114.8K3.53KJan 1993 – Sep 2000

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. 1Samedan Oil CorporationJan 1993 → Mar 1995
  2. 2Tepee Petroleum Co., Inc.Apr 1995 → Apr 2000

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
365108-99DrillSamedan Oil CorporationOct 12, 1989Oct 12, 1989—8,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-66476————

Formation tops

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

FormationMD ftSubsea
San Andres1,830533
Glorieta2,732-369
Wolfcamp5,918-3,555
Strawn7,440-5,077
MississippianMISSISSIPPI7,824-5,461
Ellenburger8,010-5,647

Perforations

Perforated and open-hole intervals.

FromToType
7,6587,663Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37532817.5350 S
8.6252,708—800 S
5.58,0357.875430 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
00Mar 22, 1990Feb 9, 1990Yes
00Mar 16, 1990——

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