TEXAS · WELLS · ROBERTS COUNTY · FLOWERS 78 LEASE · API 42-393-32370 · DISTRICT 08

Flowers 78 #5H

Plugged

Roberts County · Roberts Co. (St. Louis) field  · Horizontal

Flowers 78 #5H (API 42-393-32370) is a plugged horizontal well in Roberts County, plugged June 29, 2015, last operated by Chesapeake Operating L.L.C..

The RRC has issued one drilling permit (amended 3 times), issued June 22, 2011, permitted to 18,000 ft.

It was permitted by Chesapeake Operating, Inc. and has since transferred to Chesapeake Operating L.L.C. on the wellbore schedule.

Completion filings report 3 formation tops, including Cherokee, Morrow, Mississippian.

Operator of record

Chesapeake Operating L.L.C.

Permitted by Chesapeake Operating, Inc.; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Delinquent (D)
P-5 last filed
Sep 16, 2024
Permits on file
1,645
Phone
(405) 935-3100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChesapeake Operating L.L.C.
Production reportsnone
Latest permitChesapeake Operating, Inc.Jun 22, 2011

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

18,000
total depth, ft
4
permits on file
Jun 22, 2011
last permit issued
Sep 15, 2011
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2011 THROUGH Jun 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 15, 2011
Shut in
—
Plugged
Jun 29, 2015

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
Flowers 78 G-14-264375Roberts Co. (St. Louis)Chesapeake Operating, L.L.C.100Sep 2011 – Jun 2015

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
717227-96DrillChesapeake Operating, Inc.May 29, 2012Jun 22, 2011Jun 23, 201118,000
717227-97DrillChesapeake Operating, Inc.Nov 22, 2011Jun 22, 2011Jun 23, 201118,000
717227-98DrillChesapeake Operating, Inc.Sep 12, 2011Jun 22, 2011Jun 23, 201118,000
717227-99DrillChesapeake Operating, Inc.May 25, 2011Jun 22, 2011Jun 23, 201118,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 15, 2011Flowers 78 G-14-264375Roberts Co. (St. Louis)Chesapeake Operating L.L.C.Plugged—

Formation tops

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

FormationMD ftSubsea
Cherokee8,590-5,787
Morrow9,150-6,347
MississippianMISSISSIPPI9,628-6,825

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37572717.51,230 S
9.6255,21412.25520 S
5.510,6008.75890 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
00Aug 7, 2012Nov 17, 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/39332370, documented in the API reference.