OPERATORS · TEXAS · P-5 NUMBER 809680 · KENT COUNTY

Spi Operations LLC in Kent County

One operator, one county: its permits, wells of record, formations, and leases here, with the rest of the county and the rest of the operator one click away.

Spi Operations LLC has 1 drilling permits on file in Kent County, the first issued in 2004 and the latest on September 29, 2004.

None were issued in the last twelve months.

It is operator of record on 4 wells in the county: 0 producing, 0 shut in, 0 injection.

Its completed wells here most often report Strawn, Glorieta, Mississippian.

0
permits, 12 months
1
permits, all time since 2004
—
horizontal, 12 months
—
ft average depth, 12 months
4
wells of record
0
producing · 0 shut in · 0 injection

Permits issued by month

LAST FIVE YEARS · KENT ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Sep 29, 2004Connell "D" #2RE 551610Reenter7,700
Mar 2, 2004Connell "B" #1 542704ReenterHZ7,600
Jul 14, 1992Connell "B" #6 401198Recompletion7,841
Mar 25, 1986Connell Estate B #1 300189Recompletion7,795
May 13, 1985Connell Estate "D" #2 274749Drill7,900
Oct 2, 1984Connell Estate "D" #3 253329Drill7,900
Jun 17, 1983Connell B #6 198566Drill7,900
Oct 27, 1982Connell Estate "B" #01 175984Drill7,795

All 1 permits in Kent County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Reenter
0 / 1

12 MONTHS / ALL TIME

Leases it reports here

LeaseWellsOil, bblLast reported
Connell Estate "B"115.9KJul 2012
Connell Estate11.28KJul 2012
Connell "D"10Jul 2012
Connell "B"113.5KFeb 2012

All leases it reports → ·  Other operators in Kent County →

About this data

Permits from the RRC OGA049M master and daily daf420 files; wells of record and status from the EWA wellbore schedule, weekly; formations from the dbf900 wellbore file; leases from PDQ lease reports, placed in the county by the wells completed on them.

Developers: this page as JSON is GET /v1/data/operators/tx/809680/counties/kent, documented in the API reference.