LEASES · O-14-4156 · OIL · DISTRICT 10
McGarraugh Etal -G-
No volume since Apr 2011Apache Corporation · Ochiltree County · Horizon (Cleveland) field
Mcgarraugh Etal -G- is an RRC oil lease (O-14-4156) in Ochiltree County operated by Apache Corporation, with 5 wells completed on it.
It has reported 51.6K barrels of oil and 512K mcf of gas since January 1993, last reporting volume in April 2011 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in April 2011.
4 operators have filed production on it, most recently Apache Corporation since April 2000.
- 51.6K
- bbl oil, all reported
- 512K
- mcf gas incl. casinghead
- 0
- bbl oil, last 12 reported
- -100%
- vs the 12 before
- 5
- wells completed on it
- 1.15K
- peak month, bbl (Apr 2007)
PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME APR 2011 · 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 0 · prior 12 3,139(-100%)
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 16,124(-100%)
Who reported it
Each run of months one operator filed the production report, oldest first.
- Maxus Exploration CompanyJan 1993 → Jan 1995 · 25 mo
- Midgard Energy CompanyFeb 1995 → Sep 1997 · 32 mo
- Crescendo Resources, L.P.Oct 1997 → Mar 2000 · 30 mo
- Apache CorporationApr 2000 → Oct 2012 · 151 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
5
wells completed on the lease
- NO Type on File
- 4
- Plugged
- 1
Operates them now
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-14-4156, documented in the API reference.