WELL · 42-157-33021 · DISTRICT 3

Bryan E. Fee #27

Y

Fort Bend County · Big Creek field · Shut IN  · Vertical

Bryan E. Fee #27 (API 42-157-33021) is a well in Fort Bend County operated by Hamman Oil & Refining Company, completed March 24, 2014 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued January 16, 2014, permitted to 5,000 ft.

Completion filings report 10 formation tops, including Miocene (undifferentiated), Caprock, Catahoula, Dome Caprock - Disposal.

Its lease has reported 112K barrels of oil and 30.1K mcf of gas since March 2012, last reporting in July 2026. The lease carries 16 wells, so these are lease totals, not this well alone.

Operator of record

Hamman Oil & Refining Company

Houston, TX · P-5 Y, filed Feb 4, 2026 · 359 permits on file · (713) 254-6982

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHamman Oil & Refining Company
Production reportsHamman Oil & Refining Companythrough Apr 2026
Latest permitHamman Oil & Refining CompanyJan 16, 2014
5,000
total depth, ft
1
permits on file
Jan 16, 2014
last permit issued
Mar 24, 2014
completed
112K
cumulative oil, bbl
30.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 24, 2014
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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 lease this well is completed on; they carry 16 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bryan, E. Fee O-3-25780Big CreekHamman Oil & Refining Company16112K30.1KMar 2012 – Jul 2026

Oil, barrels lease total

Last 12 months 544 · prior 12 768(-29%)

0200400202420252026

Chain of custody

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

  1. 1Hamman Oil & Refining CompanyMay 2012 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
775176-99DrillHamman Oil & Refining CompanyDec 6, 2013Jan 16, 2014Jan 18, 20145,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-25780————

Formation tops

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

FormationMD ftSubsea
Miocene (undifferentiated)MIOCENE - DISPOSAL2,891-2,812
CaprockCAPROCK - DISPOSAL——
CatahoulaCATAHOULA - DISPOSAL——
Dome Caprock - Disposal——
FrioFRIO - DISPOSAL——
Oligocene - Disposal——
Pliocene - Disposal——
Tiger (Miocene) - Disposal——
VicksburgVICKSBURG - DISPOSAL——
WilcoxWILCOX-COCKFIELD - DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
2,0302,050Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,44312.25733 S
5.52,1847.875400 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
00Jul 25, 2014Apr 9, 2014Yes

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/15733021, documented in the API reference.