WELL · 42-441-34512 · DISTRICT 7

Wagstaff C #2

Y

Taylor County · Lake Abilene (Flippen Sand) field · Producing  · Vertical

Wagstaff C #2 (API 42-441-34512) is a well in Taylor County operated by Lariat Land & Exploration Inc., completed August 22, 2015 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 12, 2015, permitted to 2,500 ft.

Completion filings report 10 formation tops, including Coleman Junction, Flippen - Disposal, Cisco, Cook - Disposal.

Its lease has reported 10.5K barrels of oil since March 2014, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Lariat Land & Exploration Inc.

Abilene, TX · P-5 Y, filed May 4, 2026 · 25 permits on file · (325) 668-9095

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLariat Land & Exploration Inc.
Production reportsLariat Land & Exploration, Inc.through Apr 2026
Latest permitLariat Land & Exploration, Inc.May 12, 2015
2,500
total depth, ft
1
permits on file
May 12, 2015
last permit issued
Aug 22, 2015
completed
10.5K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 22, 2015
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
Wagstaff 'C' O-8-31448Lake Abilene (Flippen Sand)Lariat Land & Exploration, Inc.210.5K0Mar 2014 – Jul 2026

Oil, barrels lease total

Last 12 months 550 · prior 12 840(-35%)

050100150202420252026

Chain of custody

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

  1. 1Lariat Land & Exploration, Inc.Mar 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
806336-99DrillLariat Land & Exploration, Inc.May 7, 2015May 12, 2015Jul 27, 20152,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-31448————

Formation tops

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

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE, SW1,565420
Flippen - Disposal2,305-320
CiscoCISCO - DISPOSAL——
Cook - Disposal——
Hope Lime - Disposal——
King Sand - Disposal——
Palo PintoPALO PINTO LIME - DISPOSAL——
Saddle CreekSADDLE CREEK - DISPOSAL——
Swastika - Disposal——
Unidentified-County Regular - DI——

Perforations

Perforated and open-hole intervals.

FromToType
2,3082,311Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62512012.2580 S
5.52,3557.875300 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 19, 2015Nov 13, 2015Yes

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