LEASES · G-4-66774 · GAS · DISTRICT 04
Mecom, J. W.
No volume since Jan 1994Bluestone Natural Res. II, LLC · J. C. Martin (Lobo) field
Mecom, J. W. is an RRC gas lease (G-4-66774) in the J. C. Martin (Lobo) field operated by Bluestone Natural Res. II, LLC, with one well completed on it.
It has reported 131K mcf of gas since January 1993, last reporting volume in January 1994 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in January 1994.
7 operators have filed production on it, most recently Bluestone Natural Res. II, LLC since February 2012.
- 131K
- mcf gas, all reported
- 0
- bbl condensate and oil
- 0
- mcf gas, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- —
- peak month, bbl
PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME JAN 1994 · 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 0 · prior 12 0
Who reported it
Each run of months one operator filed the production report, oldest first.
- Coastal Oil & Gas CorporationJan 1993 → Jun 2001 · 102 mo
- EL Paso Production Oil & Gas Co.Jul 2001 → Mar 2002 · 9 mo
- United Oil & Minerals L. P.Apr 2002 → Jun 2003 · 15 mo
- United Resources, LPJul 2003 → Dec 2003 · 6 mo
- Westport Oil and Gas Company, LPJan 2004 → Feb 2006 · 26 mo
- Kerr-McGee Oil & Gas Onshore LPMar 2006 → Jan 2012 · 71 mo
- Bluestone Natural Res. II, LLCFeb 2012 → Oct 2013 · 21 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
1
wells completed on the lease
- Plugged
- 1
Operates them now
Newest permits
- — #12—
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-4-66774, documented in the API reference.