OPERATORS · TEXAS · P-5 NUMBER 712938 · PANOLA COUNTY

Rippy Oil Company in Panola 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.

Rippy Oil Company has 10 drilling permits on file in Panola County, the first issued in 2003 and the latest on December 9, 2004.

None were issued in the last twelve months.

It is not operator of record on any well in the county on the current wellbore schedule.

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

Permits issued by month

LAST FIVE YEARS · PANOLA ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Dec 9, 2004Genecov #5 554622Drill10,500
Oct 21, 2004Genecov #3 552591Recompletion10,350
Jul 14, 2004Genecov #4 548218Drill11,000
Jul 14, 2004Genecov #4 548218Drill10,300
Jul 14, 2004Genecov #4 548218Drill10,300
Jan 14, 2004Genecov #3 540734Reenter10,350
Jan 14, 2004Genecov #3 540734Reenter10,350
Nov 17, 2003Real #1 538188Reenter6,700
Feb 20, 2003Real #1 528686Reenter7,000
Feb 20, 2003Real #1 528686Reenter6,700

All 10 permits in Panola County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Reenter
0 / 5
Drill
0 / 4
Recompletion
0 / 1

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 Panola 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/712938/counties/panola, documented in the API reference.