LEASES · O-8-17277 · OIL · DISTRICT 7B

Sealy-Smith

No volume since Sep 1999

3-D Oil & Gas · Coleman County · Coleman County Regular field

Sealy-Smith is an RRC oil lease (O-8-17277) in Coleman County operated by 3-D Oil & Gas, with one well completed on it.

It has reported 2.81K barrels of oil and 680 mcf of gas since January 1993, last reporting volume in September 1999 (statewide data runs through April 2026).

The last 12 reported months total 3 barrels of oil, down 98% on the year before; the lease peaked at 124 barrels in October 1994.

2 operators have filed production on it, most recently 3-D Oil & Gas since November 1995.

2.81K
bbl oil, all reported
680
mcf gas incl. casinghead
3
bbl oil, last 12 reported
-98%
vs the 12 before
1
wells completed on it
124
peak month, bbl (Oct 1994)

PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME SEP 1999 · 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 154(-98%)

05010015019931994199519961997199819992000

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

0102019931994199519961997199819992000

Who reported it

Each run of months one operator filed the production report, oldest first.

  1. Rosson, Robert K.Jan 1993 → Oct 1995 · 34 mo
  2. 3-D Oil & GasNov 1995 → Jun 2000 · 56 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

All 1 wells, searchable →

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-8-17277, documented in the API reference.