WELL · 42-433-00099 · DISTRICT 7

Alexander Estate #2X

Plugged

Stonewall County · Alexander S. (Canyon LO) field  · Vertical

Alexander Estate #2X (API 42-433-00099) is a plugged well in Stonewall County, plugged May 14, 2014, last operated by Laneer Resources Company.

The RRC has issued one drilling permit, issued March 9, 2007, permitted to 5,960 ft.

Completion filings report one formation top, including Canyon.

Its lease has reported 112K barrels of oil and 72 mcf of gas since January 1993, last reporting in July 2026. The lease carries 21 wells, so these are lease totals, not this well alone.

Operator of record

Laneer Resources Company

Abilene, TX · P-5 Y, filed Apr 4, 2026 · 61 permits on file · (325) 669-4752

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLaneer Resources Company
Production reportsLaneer Resources Companythrough Apr 2026
Latest permitLaneer Resources CompanyMar 9, 2007
5,960
total depth, ft
1
permits on file
Mar 9, 2007
last permit issued
—
completed
112K
cumulative oil, bbl
72
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
May 14, 2014

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 21 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Alexander Estate O-8-15792Alexander, S. (Canyon, LO)Laneer Resources Company21112K72Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 2,270 · prior 12 3,079(-26%)

0200400600202420252026

Chain of custody

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

  1. 1Laneer Resources CompanyJan 1993 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
634356-99ReenterLaneer Resources CompanyFeb 28, 2007Mar 9, 2007Jun 20, 20075,960

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-15792————

Formation tops

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

FormationMD ftSubsea
CanyonCANYON SAND4,798-3,086

Perforations

Perforated and open-hole intervals.

FromToType
4,7984,804Perforated
4,8104,820Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.75130—65 S
—1907.875150 S
—4,5687.875900 S
4.54,842—245 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
00Nov 14, 2008Dec 10, 2007Yes
00Oct 10, 2008——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
Sep 2014
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000097294H-1 InjectionPlugged Jun 5, 20142251,8004,798–4,820

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120132014

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