WELL · 42-115-33990 · DISTRICT 8

Heartsbane 38-47 A #2DN

Y

Dawson County · Spraberry (Trend Area) field · Producing  · Horizontal

Heartsbane 38-47 A #2DN (API 42-115-33990) is a horizontal well in Dawson County operated by Birch Operations Inc., completed October 18, 2024 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 28, 2024, permitted to 8,700 ft.

Completion filings report 10 formation tops, including Yates, San Andres, Spraberry, Dean.

Its lease has reported 430K barrels of oil and 295K mcf of gas since October 2024, last reporting in July 2026.

Operator of record

Birch Operations Inc.

Houston, TX · P-5 Y, filed Jan 4, 2026 · 619 permits on file · (713) 238-6071

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBirch Operations Inc.
Production reportsBirch Operations, Inc.through Apr 2026
Latest permitBirch Operations, Inc.May 28, 2024
8,700
total depth, ft
1
permits on file
May 28, 2024
last permit issued
Oct 18, 2024
completed
430K
cumulative oil, bbl
295K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2024 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 18, 2024
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

32.580359, -101.722376

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Dawson County.

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
Heartsbane 38-47 A O-10-63152Spraberry (Trend Area)Birch Operations, Inc.1430K295KOct 2024 – Jul 2026

Oil, barrels lease total

Last 12 months 186,413 · prior 12 244,043(-24%)

020K40K60K202420252026

Gas, mcf lease total

Last 12 months 175,943 · prior 12 118,871(+48%)

010K20K30K202420252026

Chain of custody

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

  1. 1Birch Operations, Inc.Oct 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
899930-99DrillBirch Operations, Inc.May 22, 2024May 28, 2024Jun 1, 20248,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-63152————

Formation tops

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

FormationMD ftSubsea
Yates2,103735
San AndresSAN ANDRES - ACTIVE CO2 FLOOD; H3,590-752
Spraberry6,868-4,030
Dean8,259-5,421
Canyon——
Devonian——
Mississippian——
Pennsylvanian——
Silurian (undifferentiated)SILURIAN——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
8,61218,970Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37549717.5525 S
9.6257,76412.251,075 S
5.519,0218.51,970 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
00May 23, 2025Apr 17, 2025Yes

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) and the University Lands library. then paste it into their search.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Heartsbane 38-47 C42-115-33991

0.0 KM · Birch Operations, Inc. · Section with this well →

Yates2,101737
San Andres3,582-744
Clear Fork4,751-1,913
Spraberry6,863-4,025
Dean8,247-5,409
Wolfcamp—
Pennsylvanian—
Mississippian—

10 TOPS · FIRST 8

Ghost 35-26 C42-115-33958

0.0 KM · Birch Operations, Inc. · Section with this well →

Yates2,105732
San Andres3,405-568
Clear Fork4,713-1,876
Spraberry6,850-4,013
Dean8,243-5,406
Canyon—
Wolfcamp—
Mississippian—

10 TOPS · FIRST 8

Ghost 35-26 B42-115-33921

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates2,126711
San Andres3,423-586
Clear Fork4,744-1,907
Spraberry6,878-4,041
Dean8,262-5,425
Devonian—
Canyon—
Wolfcamp—

10 TOPS · FIRST 8

Ghost 35-26 A42-115-33920

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates2,129708
San Andres3,442-605
Clear Fork4,778-1,941
Spraberry6,897-4,060
Dean8,280-5,443
Mississippian—
Devonian—
Canyon—

10 TOPS · FIRST 8

Lady Stoneheart 38-47 B42-115-33919

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates2,135702
San Andres3,601-764
Clear Fork4,752-1,915
Spraberry6,880-4,043
Dean8,267-5,430
Canyon—
Devonian—
Mississippian—

10 TOPS · FIRST 8

Lady Stoneheart 38-47 A42-115-33918

0.5 KM · Birch Operations, Inc. · Section with this well →

Yates2,123714
San Andres3,598-761
Clear Fork4,779-1,942
Spraberry6,894-4,057
Dean8,285-5,448
Pennsylvanian—
Wolfcamp—
Canyon—

10 TOPS · FIRST 8

Moon Door 36-25 A42-115-33971

0.7 KM · Birch Operations, Inc. · Section with this well →

Yates2,107729
San Andres3,409-573
Clear Fork4,704-1,868
Spraberry6,864-4,028
Dean8,241-5,405
Canyon—
Devonian—
Mississippian—

10 TOPS · FIRST 8

Moon Door 36-25 C42-115-33972

0.7 KM · Birch Operations, Inc. · Section with this well →

Yates2,108728
San Andres3,415-579
Clear Fork4,685-1,849
Spraberry6,845-4,009
Dean8,220-5,384
Canyon—
Wolfcamp—
Pennsylvanian—

10 TOPS · FIRST 8

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