TEXAS · WELLS · DAWSON COUNTY · JAMES BROWN 18 LEASE · API 42-115-33372 · DISTRICT 7B

James Brown 18 #1

Y

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

James Brown 18 #1 (API 42-115-33372) is a well in Dawson County operated by Diamondback E&P LLC, completed April 27, 2011 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued February 18, 2011, permitted to 11,420 ft.

It was permitted by Element Petroleum Operating, LLC and has since transferred to Diamondback E&P LLC on the wellbore schedule.

Completion filings report 5 formation tops, including Spraberry, Wolfcamp, Cline, Strawn.

Its lease has reported 72.2K barrels of oil and 54K mcf of gas since April 2011, last reporting volume in April 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Diamondback E&P LLC

Permitted by Element Petroleum Operating, LLC; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active – Extension (X)
P-5 last filed
May 4, 2026
Permits on file
5,251
Phone
(432) 221-7400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDiamondback E&P LLC
Production reportsDiamondback E&P LLCthrough Apr 2026
Latest permitElement Petroleum Operating, LLCFeb 18, 2011

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

11,420
total depth, ft
2
permits on file
Feb 18, 2011
last permit issued
Apr 27, 2011
completed
72.2K
cumulative oil, bbl
54K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2011 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 27, 2011
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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
James Brown 18 O-10-41145Spraberry (Trend Area)Diamondback E&P LLC272.2K54KApr 2011 – Apr 2026

Oil, barrels lease total

Last 12 months 1,558 · prior 12 2,062(-24%)

0200400202420252026

Gas, mcf lease total

Last 12 months 2,249 · prior 12 2,185(+3%)

0200400202420252026

Chain of custody

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

  1. 1Element Petro Operating II, LLCApr 2011 → Sep 2013
  2. 2Diamondback E&P LLCOct 2013 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
710422-98DrillElement Petroleum Operating, LLCFeb 22, 2011Feb 18, 2011Feb 24, 201112,000
710422-99DrillElement Petroleum Operating, LLCFeb 16, 2011Feb 18, 2011—11,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 27, 2011James Brown 18 O-10-41145Spraberry (Trend Area)Diamondback E&P LLCProducing11,420

Formation tops

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

FormationMD ftSubsea
SpraberryLOWER SPRABERRY8,640-5,730
Wolfcamp9,477-6,567
Cline10,356-7,446
StrawnSTRAWN LIME10,847-7,937
AtokaATOKA SHALE10,990-8,080
AtokaATOKA LIME11,049-8,139

Perforations

Perforated and open-hole intervals.

FromToType
9,2739,370Perforated
9,5279,755Perforated
9,8139,976Perforated
10,29810,407Perforated
10,46110,633Perforated
10,69710,860Perforated
10,96511,132Perforated
11,21811,276Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37537617.5350 S
8.6254,413111,700 S
5.511,4087.8751,225 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
00Feb 2, 2012Jun 3, 2011Yes

Well logs

2 logs loaded from the RRC's log index, the latest received Apr 7, 2014. Density, Neutron. 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 POROSITYSpans Spraberry, Wolfcamp, Cline, Strawn, AtokaTIFF100 to 11,301Apr 7, 2014run Mar 12, 20113.33
NEUTRON/DENSITY POROSITYSpans Spraberry, Wolfcamp, Cline, Strawn, AtokaTIFF100 to 11,301Mar 19, 2014run Mar 12, 20113.75

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