TEXAS · WELLS · CROCKETT COUNTY · API 42-105-39366 · DISTRICT 6E

Davidson #3507

On schedule

Crockett County · Ozona NE. (Canyon Sand) field · SWR-10-Well  · Vertical

Fields on the latest permit · any of 2
Davidson Ranch (Penn. 7890) · Ozona, NE. (Canyon Sand)
Not one formation; the well must be completed in one of them, and no target formation is stated.

Davidson #3507 (API 42-105-39366) is a well in Crockett County operated by Scout Energy Management LLC, completed February 1, 2005 and listed as swr-10-well on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued July 26, 2004, permitted to 8,300 ft.

It was permitted by Anadarko E&P Company LP and has since transferred to Scout Energy Management LLC on the wellbore schedule.

Completion filings report 5 formation tops, including B Lime, Top B Lime, Ozona (Canyon), Top Ozona (Canyon).

Its 2 leases have reported 541K mcf of gas since February 2005, last reporting volume in August 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Scout Energy Management LLC

Permitted by Anadarko E&P Company LP; the EWA schedule now lists a different operator.

Based in
Dallas, TX
P-5 status
Active – Extension (X)
P-5 last filed
Oct 20, 2026
Permits on file
483
Phone
(972) 277-1397

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleScout Energy Management LLC
Production reportsScout Energy Management LLCthrough Aug 2026
Latest permitAnadarko E&P Company LPJul 26, 2004

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

8,300
total depth, ft
2
permits on file
Jul 26, 2004
last permit issued
Feb 1, 2005
completed
0
cumulative oil, bbl
541K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · FEB 2005 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 1, 2005
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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
Davidson G-9-209329Davidson Ranch (Penn. 7890)Scout Energy Management LLC10541KFeb 2005 – Aug 2026
Davidson G-9-209331Ozona, NE. (Canyon Sand)Scout Energy Management LLC100Feb 2005 – —

Gas, mcf lease total

Last 12 months 8,749 · prior 12 7,125(+23%)

05001K202420252026

Wells named Davidson

Scout Energy Management LLC's other wells filed under this lease name in Crockett 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. 1Anadarko E&P Company LPFeb 2005 → Dec 2012
  2. 2Anadarko E&P Onshore LLCJan 2013 → Aug 2016
  3. 3Epic Permian Operating, LLCSep 2016 → Jan 2025
  4. 4Scout Energy Management LLCFeb 2025 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
548585-98DrillAnadarko E&P Company LPOct 7, 2004Jul 26, 2004Dec 26, 20049,000
548585-99DrillAnadarko E&P Company LPJul 21, 2004Jul 26, 2004—9,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 1, 2005Davidson G-9-209331Ozona NE. (Canyon Sand)Scout Energy Management LLCSWR-10-Well · shut in Mar 1, 20058,300
Feb 1, 2005Davidson G-9-209329Davidson Ranch (Penn. 7890)Scout Energy Management LLCProducing8,300

Formation tops

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

FormationMD ftSubsea
B Lime5,738-3,304
Top B Lime5,738-3,304
Ozona (Canyon)6,080-3,646
Top Ozona (Canyon)6,080-3,646
PennsylvanianPENN7,822-5,388
PennsylvanianTOP PENN7,822-5,388

Perforations

Perforated and open-hole intervals.

FromToType
6,1746,196Perforated
7,8357,954Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62593111310 S
4.58,2787.875670 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
00Sep 15, 2005Apr 1, 2005—
00Sep 13, 2005Apr 1, 2005Yes
00Jul 13, 2005——

Well logs

The RRC's map lists this well among those with logs online. Its monthly inventories loaded here, which start in July 2006, list none for it, so none are itemized.

Open the RRC's log search for this well ↗

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. The University Lands library has no per-well link: then paste it into its 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/10539366, documented in the API reference.