LEASES · G-14-166703 · GAS · DISTRICT 10
Courson -B- 4
ReportingLatigo Petroleum, LLC · Roberts County · Lips, West (Cleveland), Pan Petro (Cleveland) field
Courson -B- 4 is an RRC gas lease (G-14-166703) in Roberts County operated by Latigo Petroleum, LLC, with one well completed on it.
It has reported 1.08M mcf of gas since October 1996, last reporting volume in March 2026 (statewide data runs through April 2026).
The last 12 reported months total 2.41K mcf of gas.
4 operators have filed production on it, most recently Latigo Petroleum, LLC since May 2016.
- 1.08M
- mcf gas, all reported
- 0
- bbl condensate and oil
- 2.41K
- mcf gas, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- —
- peak month, bbl
PDQ LEASE REPORTS · FIRST OCT 1996 · LAST VOLUME MAR 2026 · STATEWIDE DATA THROUGH APR 2026
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 2,408 · prior 12 5,469(-56%)
Decline curve
None shown. Petrora fits an Arps curve only when the last ten years of gas reports follow one decline closely enough to project (R² of 0.7 or better over at least a year since the peak). This lease's recent history does not, so a projection would be a guess dressed as a number.
Who reported it
Each run of months one operator filed the production report, oldest first.
- Crescendo Resources, L.P.Oct 1996 → Mar 2000 · 42 mo
- Amoco Production CompanyApr 2000 → Dec 2001 · 21 mo
- BP America Production CompanyJan 2002 → Apr 2016 · 172 mo
- Latigo Petroleum, LLCMay 2016 → Jul 2026 · 123 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/g-14-166703, documented in the API reference.