WELL · 42-429-36216 · DISTRICT 7

Bill Echols #10

Y

Stephens County · Jett Reed (Strawn) field · Producing  · Vertical

Bill Echols #10 (API 42-429-36216) is a well in Stephens County operated by Echols Oil Company L.L.C., completed June 12, 2006 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 15, 2006, permitted to 3,100 ft.

It was permitted by Echols Oil Company and has since transferred to Echols Oil Company L.L.C. on the wellbore schedule.

Completion filings report one formation top, including Strawn.

Its lease has reported 31.3K barrels of oil and 46.4K mcf of gas since October 2005, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Echols Oil Company L.L.C.

Permitted by Echols Oil Company; the EWA schedule now lists a different operator.

Caddo, TX · P-5 Y, filed Nov 4, 2025 · (254) 559-3935

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEchols Oil Company L.L.C.
Production reportsEchols Oil Company, L.L.C.through Apr 2026
Latest permitEchols Oil CompanyMar 15, 2006

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

3,100
total depth, ft
1
permits on file
Mar 15, 2006
last permit issued
Jun 12, 2006
completed
31.3K
cumulative oil, bbl
46.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 12, 2006
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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bill Echols O-8-29732Jett Reed (Strawn)Echols Oil Company, L.L.C.231.3K46.4KOct 2005 – Jul 2026

Oil, barrels lease total

Last 12 months 155 · prior 12 130(+19%)

02040202420252026

Chain of custody

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

  1. 1Echols Oil CompanyOct 2005 → Jan 2012
  2. 2Echols Oil Company, L.L.C.Feb 2012 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
615404-99DrillEchols Oil CompanyMar 7, 2006Mar 15, 2006—3,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-29732————

Formation tops

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

FormationMD ftSubsea
Strawn2,584-1,347

Perforations

Perforated and open-hole intervals.

FromToType
2,5842,600Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62515812.25110 S
4.52,7157.875110 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
00Jan 23, 2007Jul 6, 2006Yes
00Aug 17, 2006——

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