TEXAS · WELLS · SAN AUGUSTINE COUNTY · BSI/USFS F6 DU LEASE · API 42-405-30625 · DISTRICT 06

Bsi/Usfs F6 Du #B 4

Y

San Augustine County · Carthage (Haynesville Shale) field · Producing  · Horizontal

Bsi/Usfs F6 Du #B 4 (API 42-405-30625) is a horizontal well in San Augustine County operated by Xto Energy Inc., completed June 15, 2018 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 28, 2017, permitted to 13,894 ft.

Completion filings report 4 formation tops, including Austin Chalk, James Lime, Bossier, Haynesville.

Its lease has reported 12.9M mcf of gas since November 2017, last reporting volume in April 2026.

Operator of record

XTO Energy Inc.

Based in
Spring, TX
P-5 status
Active – Extension (X)
P-5 last filed
Apr 8, 2026
Permits on file
16,156
Phone
(346) 502-1572

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsXTO Energy Inc.through Apr 2026
Latest permitXTO Energy Inc.Mar 28, 2017
13,894
total depth, ft
1
permits on file
Mar 28, 2017
last permit issued
Jun 15, 2018
completed
0
cumulative oil, bbl
12.9M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2018 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 15, 2018
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Bsi/Usfs F6 Du G-6-283175Carthage (Haynesville Shale)XTO Energy Inc.1012.9MNov 2017 – Apr 2026

Gas, mcf lease total

Last 12 months 338,495 · prior 12 425,378(-20%)

020K40K60K202420252026

Chain of custody

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

  1. 1XTO Energy Inc.Jun 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
824432-99DrillXTO Energy Inc.Mar 14, 2017Mar 28, 2017Jun 13, 201720,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jun 15, 2018Bsi/Usfs F6 Du G-6-283175Carthage (Haynesville Shale)XTO Energy Inc.Producing13,894

Formation tops

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

FormationMD ftSubsea
Austin Chalk4,897-4,598
James Lime8,164-7,865
Bossier13,590-13,291
Haynesville13,940-13,641

Perforations

Perforated and open-hole intervals.

FromToType
13,00622,840Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,87513.51,420 S
7.2513,0069.8752,130 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jan 14, 2019Aug 15, 2018—
00Feb 9, 2018Nov 15, 2017Yes

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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