OPERATORS · TEXAS · P-5 NUMBER 435400 · WILBARGER COUNTY

Johnson, F. T., Jr. in Wilbarger 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.

Johnson, F. T., Jr. has 100 drilling permits on file in Wilbarger County, the first issued in 1977 and the latest on May 17, 1991.

None were issued in the last twelve months.

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

0
permits, 12 months
100
permits, all time since 1977
—
horizontal, 12 months
—
ft average depth, 12 months
68
wells of record
0
producing · 0 shut in · 0 injection

Permits issued by month

LAST FIVE YEARS · WILBARGER ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
May 17, 1991Waggoner "P" #18 387835Drill2,000
Mar 19, 1990Waggoner "PQ" #23 370995Drill2,500
Oct 4, 1985Waggoner "DD" #11 286799Drill2,500
Apr 1, 1985Baker #8 271173Drill1,500
Apr 1, 1985Sullivan #1 271137Drill2,500
Oct 9, 1984Baker #7 253906Drill1,500
Feb 1, 1984Shepherd #1 228001Drill8,000
Nov 21, 1983Waggoner "EE" #8 221069Drill2,600
Oct 31, 1983Rutherford #1 219212Drill7,000
Sep 2, 1983Dockery #5 209404Drill7,000

All 100 permits in Wilbarger County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 100

12 MONTHS / ALL TIME

Formations reported

No completion tops on file for its wells here.

Leases it reports here

No leases with wells completed in this county carry this operator's production reports.

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