WELL · 42-049-34779 · DISTRICT 7

Thomas #1

N

Brown County · Brown County Regular field  · Vertical

Thomas #1 (API 42-049-34779) is a well in Brown County operated by Hane Operating Inc., completed April 6, 1987.

The RRC has issued one drilling permit, issued February 23, 1987, permitted to 3,000 ft.

It was permitted by Bee-Jay Energy and has since transferred to Hane Operating Inc. on the wellbore schedule.

Completion filings report one formation top, including Caddo.

Its 2 leases have reported 327 barrels of oil and 12.1K mcf of gas since January 1993, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Hane Operating Inc.

Permitted by Bee-Jay Energy; the EWA schedule now lists a different operator.

Santa Anna, TX · P-5 Y, filed Jun 10, 2005 · 12 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHane Operating Inc.
Production reportsHane Operating, Inc.through Jun 1998
Latest permitBee-Jay EnergyFeb 23, 1987

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

3,000
total depth, ft
1
permits on file
Feb 23, 1987
last permit issued
Apr 6, 1987
completed
327
cumulative oil, bbl
12.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 6, 1987
Shut in
—
Plugged
—

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Thomas G-8-186689Brown County RegularThomas, Louis W.100May 2001 – Jul 2026
Thomas O-8-24285Brown County RegularHane Operating, Inc.132712.1KJan 1993 – Feb 2002

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Bee-Jay EnergyJan 1993 → Nov 1993
  2. 2Bee-Jay Petro, Inc.Dec 1993 → Nov 1997
  3. 3Hane Operating, Inc.Dec 1997 → Jun 1998

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
326821-99DrillBee-Jay EnergyFeb 19, 1987Feb 23, 1987—3,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-186689————
—— O-8-24285————

Formation tops

As filed on W-2/G-1. Subsea from 1,524 ft elevation.Download CSV →

FormationMD ftSubsea
Caddo1,580-56

Perforations

Perforated and open-hole intervals.

FromToType
2,4502,540Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62533712.25155 S
8.62533712.75155 S
4.52,7937.875460 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Feb 19, 2002May 30, 2001—
00Feb 5, 2002——
00May 1, 1987Apr 27, 1987Yes
00Apr 30, 1987——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/04934779, documented in the API reference.