WELL · 42-295-33655 · DISTRICT 10

Brainard 61 #1

Y

Lipscomb County · Parsell (Morrow Lower) field · Producing  · Horizontal

Brainard 61 #1 (API 42-295-33655) is a horizontal well in Lipscomb County operated by Corlena Oil Company, completed July 7, 2011 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended twice), issued February 3, 2011, permitted to 14,000 ft.

Completion filings report 10 formation tops, including Brown Dolomite, Heebner Shale, Tonkawa, Cottage Grove.

No lease production has been reported under this well’s leases.

Operator of record

Corlena Oil Company

Based in
Amarillo, TX
P-5 status
Active (A)
P-5 last filed
Jun 26, 2026
Permits on file
132
Phone
(806) 372-5044

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCorlena Oil Company
Production reportsCorlena Oil Companythrough Apr 2026
Latest permitCorlena Oil CompanyFeb 3, 2011
14,000
total depth, ft
3
permits on file
Feb 3, 2011
last permit issued
Jul 7, 2011
completed
0
cumulative oil, bbl
4.58M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 7, 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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Brainard 61 G-14-264797Parsell (Morrow, Lower)Corlena Oil Company104.58MJul 2011 – Jul 2026

Gas, mcf lease total

Last 12 months 35,353 · prior 12 22,215(+59%)

02K4K6K202420252026

Chain of custody

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

  1. 1Corlena Oil CompanyJul 2011 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
709559-97DrillCorlena Oil CompanyJul 11, 2011Feb 3, 2011May 6, 201114,000
709559-98DrillCorlena Oil CompanyMar 22, 2011Feb 3, 2011May 4, 201114,000
709559-99DrillCorlena Oil CompanyFeb 1, 2011Feb 3, 2011May 4, 201111,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-264797————

Formation tops

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

FormationMD ftSubsea
Brown Dolomite3,623-902
Heebner Shale6,385-3,664
TonkawaTONKAWA SAND7,090-4,369
Cottage Grove7,767-5,046
ClevelandCLEVELAND SAND8,078-5,357
MarmatonMARMATON LIME8,523-5,802
13 Finger Lmst9,793-7,072
Squawbelly Lmst10,776-8,055
Parsell Sand11,131-8,410
MorrowLOWER MORROW SAND11,211-8,490

Perforations

Perforated and open-hole intervals.

FromToType
11,13411,150Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,61312.51,190 S
710,5258.75340 S
4.511,3956.12575 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
00Sep 28, 2012Sep 27, 2011Yes

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