OPERATORS · TEXAS · P-5 NUMBER 493400 · KING COUNTY

Leclair Operating Co., Inc. in King 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.

Leclair Operating Co., INC. has 12 drilling permits on file in King County, the first issued in 1992 and the latest on March 3, 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 Tannehill, Coleman Junction.

0
permits, 12 months
12
permits, all time since 1992
—
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 · KING ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Mar 3, 2004Springer, G #4 542768Drill4,000
Jan 16, 2004Springer, G. #3 540719Drill4,000
Jul 15, 2003G. Springer #2 534152Drill4,000
Jul 15, 2003Springer, G. #1 534151Drill4,000
Apr 19, 2000Simpson #9 494145Drill3,900
Nov 24, 1999Simpson #8 489632Drill3,500
Jul 21, 1999Simpson #7 485948Drill3,500
Jan 19, 1999Simpson #6 482035Drill3,500
Dec 19, 1997Simpson #5 471095Drill3,500
Apr 7, 1995Simpson #3 434246Drill3,500

All 12 permits in King County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 12

12 MONTHS / ALL TIME

Formations reported

Leases it reports here

LeaseWellsOil, bblLast reported
Springer, W. A.123.1KOct 2009
Carothers, G. C.422KSep 2007

All leases it reports → ·  Other operators in King 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/493400/counties/king, documented in the API reference.