LEASES · O-3-16228 · OIL · DISTRICT 03
Arco Fee
No volume since Mar 2018Cameron Exploration, Inc. · Jasper County · Champion (Wilcox 9050) field
Arco Fee is an RRC oil lease (O-3-16228) in Jasper County operated by Cameron Exploration, Inc., with one well completed on it.
It has reported 31.1K barrels of oil and 3.55K mcf of gas since January 1993, last reporting volume in March 2018 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in March 2018.
6 operators have filed production on it, most recently Cameron Exploration, Inc. since June 2018.
- 31.1K
- bbl oil, all reported
- 3.55K
- mcf gas incl. casinghead
- 0
- bbl oil, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- 591
- peak month, bbl (Dec 1996)
PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME MAR 2018 · 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 0
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.
- Ballard Exploration Company,inc.Jan 1993 → Oct 2003 · 130 mo
- Morris, W. Dale Inc.Nov 2003 → Jul 2004 · 9 mo
- Chaparral Energy, L.L.C.Aug 2004 → Jul 2012 · 96 mo
- Five-Jab, Inc.Aug 2012 → Nov 2014 · 28 mo
- Jeffcoat Production Company Inc.Dec 2014 → May 2018 · 42 mo
- Cameron Exploration, Inc.Jun 2018 → Feb 2025 · 81 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-3-16228, documented in the API reference.