WELL · 42-503-40270 · DISTRICT 9

Larimore #1

Plugged

Young County · Newcastle NE. (Congl.) field  · Vertical

Larimore #1 (API 42-503-40270) is a plugged well in Young County, plugged January 14, 2008, last operated by Larimore Larry.

The RRC has issued one drilling permit (amended once), issued December 5, 1990, permitted to 4,900 ft.

It was permitted by Western Reserves Corporation and has since transferred to Larimore Larry on the wellbore schedule.

Completion filings report 3 formation tops, including Caddo, Conglomerate, Mississippian.

Its lease has reported 5.78K barrels of oil and 23 mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Larimore Larry

Permitted by Western Reserves Corporation; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Dec 7, 2007 · 2 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLarimore Larry
Production reportsLarimore, Larrythrough Feb 2007
Latest permitWestern Reserves CorporationDec 5, 1990

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

4,900
total depth, ft
2
permits on file
Dec 5, 1990
last permit issued
Jan 7, 1991
completed
5.78K
cumulative oil, bbl
23
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 7, 1991
Shut in
—
Plugged
Jan 14, 2008

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Larimore O-13-27915Newcastle, NE. (Congl.)Larimore, Larry15.78K23Jan 1993 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Western Reserves CorporationJan 1993 → Feb 2000
  2. 2Larimore, LarryMar 2000 → Feb 2007

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
381718-98DrillWestern Reserves CorporationJan 31, 1991Dec 5, 1990Dec 11, 19904,900
381718-99DrillWestern Reserves CorporationNov 30, 1990Dec 5, 1990—4,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-27915————

Formation tops

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

FormationMD ftSubsea
Caddo3,840-2,680
Conglomerate4,333-3,173
MississippianMISSISSIPPIAN REEF4,700-3,540

Perforations

Perforated and open-hole intervals.

FromToType
3,8803,890Perforated
4,3334,339Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62546011—
4.54,6967.875—

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
00Aug 4, 2005Feb 28, 2005—
00Apr 15, 1991Jan 30, 1991Yes
00Feb 27, 1991——

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