WELL · 42-435-36418 · DISTRICT 7

Fbe 17-5 #1705

Y

Sutton County · Sawyer (Canyon) field · Producing  · Vertical

Fbe 17-5 #1705 (API 42-435-36418) is a well in Sutton County operated by Henry Petroleum LLC, completed August 20, 2003 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 10, 2003, permitted to 8,500 ft.

It was permitted by Falcon Bay Energy, L.L.C and has since transferred to Henry Petroleum LLC on the wellbore schedule.

Completion filings report one formation top, including Canyon.

No lease production has been reported under this well’s leases.

Operator of record

Henry Petroleum LLC

Permitted by Falcon Bay Energy, L.L.C; the EWA schedule now lists a different operator.

Flower Mound, TX · P-5 Y, filed Jun 4, 2026 · (972) 754-6281

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHenry Petroleum LLC
Production reportsHenry Petroleum LLCthrough Feb 2026
Latest permitFalcon Bay Energy, L.L.CJul 10, 2003

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

8,500
total depth, ft
1
permits on file
Jul 10, 2003
last permit issued
Aug 20, 2003
completed
0
cumulative oil, bbl
108K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 20, 2003
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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Fbe 17-5 G-9-201015Sawyer (Canyon)Henry Petroleum LLC10108KAug 2003 – Jul 2026

Gas, mcf lease total

Last 12 months 154 · prior 12 186(-17%)

0204060202420252026

Chain of custody

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

  1. 1Falcon Bay Energy, L.L.CAug 2003 → Jan 2005
  2. 2Falcon Bay Operations, LLCFeb 2005 → May 2006
  3. 3Foundation Energy Management LLCJun 2006 → Sep 2015
  4. 4Henry Petroleum LLCOct 2015 → Feb 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
533696-99DrillFalcon Bay Energy, L.L.CJun 30, 2003Jul 10, 2003Jul 28, 20038,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-201015————

Formation tops

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

FormationMD ftSubsea
CanyonUPPER CANYON5,442-3,412
CanyonLOWER CANYON7,281-5,251

Perforations

Perforated and open-hole intervals.

FromToType
7,2847,348Perforated
7,5707,830Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,34811375 S
4.57,9937.875725 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 23, 2004Mar 17, 2004Yes
00May 17, 2004——

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