TEXAS · WELLS · JOHNSON COUNTY · API 42-251-31008 · DISTRICT 7C

White Wing Coachman A #3H

Plugged

Johnson County · Newark East (Barnett Shale) field  · Horizontal

White Wing Coachman A #3H (API 42-251-31008) is a plugged horizontal well in Johnson County, plugged January 11, 2024, last operated by Tep Barnett USA LLC.

The RRC has issued one drilling permit, issued May 31, 2006, permitted to 9,000 ft.

It was permitted by Chesapeake Operating, Inc. and has since transferred to Tep Barnett USA LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Atoka, Upr Barnett.

Its 2 leases have reported 895K mcf of gas since February 2006, with no volume in the three years through August 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

TEP Barnett USA LLC

Permitted by Chesapeake Operating, Inc.; the EWA schedule now lists a different operator.

Based in
Fort Worth, TX
P-5 status
Active (A)
P-5 last filed
Apr 10, 2026
Permits on file
371
Phone
(817) 720-1100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTEP Barnett USA LLC
Production reportsTEP Barnett USA, LLCthrough Feb 2012
Latest permitChesapeake Operating, Inc.May 31, 2006

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

9,000
total depth, ft
1
permits on file
May 31, 2006
last permit issued
Oct 6, 2006
completed
0
cumulative oil, bbl
895K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · OCT 2006 THROUGH FEB 2012

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 6, 2006
Shut in
—
Plugged
Jan 11, 2024

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 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
White Wing Coachman "A" G-13-226119Newark, East (Barnett Shale)TEP Barnett USA, LLC10895KOct 2006 – Feb 2012
Tarrant Minerals "B" G-13-227261Newark, East (Barnett Shale)Chesapeake Operating, Inc.100Feb 2006 – —

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

Wells named White Wing Coachman A

TEP Barnett USA LLC's other wells filed under this lease name in Johnson County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Chesapeake Operating, Inc.Oct 2006 → Feb 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
620126-99DrillChesapeake Operating, Inc.May 30, 2006May 31, 2006Jul 5, 20069,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 6, 2006White Wing Coachman A G-13-226119Newark East (Barnett Shale)TEP Barnett USA LLCPlugged—
—Tarrant Minerals B G-13-227261Newark East (Barnett Shale)Chesapeake Operating Inc.Plugged—

Formation tops

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

FormationMD ftSubsea
AtokaATOKA LIME5,944-4,997
AtokaBASAL ATOKA6,271-5,324
Upr Barnett6,368-5,421

Perforations

Perforated and open-hole intervals.

FromToType
7,0807,787Perforated
7,9868,693Perforated
8,8929,600Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,33512.25520 S
5.59,7367.875920 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
00Jun 25, 2007——
00May 1, 2007Dec 29, 2006Yes
00Apr 23, 2007——

Well logs

2 logs loaded from the RRC's log index, the latest received Aug 24, 2009. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
NEUTRON/DENSITY POROSITYTIFF1,354 to 5,932Aug 24, 2009run Jul 17, 20063.26
RESISTIVITYSpans AtokaTIFF1,354 to 5,945Aug 24, 2009run Jul 17, 20062.20

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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