LEASES · O-10-26445 · OIL · DISTRICT 08
Eaton -A-
No volume since Jul 2003Topat Oil Corporation · Pecos County · Abell (Permian-General) field
Eaton -A- is an RRC oil lease (O-10-26445) in Pecos County operated by Topat Oil Corporation, with one well completed on it.
It has reported 188 barrels of oil and 99 mcf of gas since January 1993, last reporting volume in July 2003 (statewide data runs through April 2026).
The last 12 reported months total 3 barrels of oil; the lease peaked at 45 barrels in September 1994.
6 operators have filed production on it, most recently Topat Oil Corporation since December 2002.
- 188
- bbl oil, all reported
- 99
- mcf gas incl. casinghead
- 3
- bbl oil, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- 45
- peak month, bbl (Sep 1994)
PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME JUL 2003 · STATEWIDE DATA THROUGH APR 2026
Oil by month
Barrels reported on Form PR for the whole lease. The latest months are revised upward as late reports arrive.
Last 12 months 3 · prior 12 5(-40%)
Gas by month
Gas-well gas plus casinghead gas, mcf. On an oil lease all gas is reported as casinghead. The latest months are revised upward as late reports arrive.
Last 12 months 0 · prior 12 0
Who reported it
Each run of months one operator filed the production report, oldest first.
- Ormand, Don R.Jan 1993 → Mar 1994 · 15 mo
- Sentry Exploration, Inc.Apr 1994 → Jun 1994 · 3 mo
- Skaar, K. M. Oil & Gas Co.Jul 1994 → Aug 1995 · 14 mo
- Halmat PetroleumSep 1995 → Feb 1998 · 30 mo
- Covenant Production Co., L.C.Mar 1998 → Nov 2002 · 57 mo
- Topat Oil CorporationDec 2002 → May 2004 · 18 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
About this data
Monthly oil, gas, and casinghead from the RRC PDQ production dump, which lags the reporting month by two to three months; figures shown through Apr 2026. Wells from completion reports; operator runs from who filed each month's report.
Developers: this page as JSON is GET /v1/data/leases/tx/o-10-26445, documented in the API reference.