WELL · 42-195-30890 · DISTRICT 10

Flowers -A- #1

Plugged

Hansford County · Hansford (Morrow Upper) field  · Vertical

Flowers -A- #1 (API 42-195-30890) is a plugged well in Hansford County, plugged May 20, 2002, last operated by BP America Production Company.

The RRC has issued one drilling permit, issued June 14, 1983, permitted to 7,400 ft.

It was permitted by Txo Production Corp. and has since transferred to BP America Production Company on the wellbore schedule.

Completion filings report 5 formation tops, including Tonkawa, Kansas City, Des Moines, Atoka.

Operator of record

BP America Production Company

Permitted by TXO Production Corp.; the EWA schedule now lists a different operator.

Denver, CO · P-5 Y, filed May 4, 2026 · 1,623 permits on file · (720) 439-5104

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBP America Production Company
Production reportsBP America Production Companythrough May 2002
Latest permitTXO Production Corp.Jun 14, 1983

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

7,400
total depth, ft
1
permits on file
Jun 14, 1983
last permit issued
Jul 14, 1983
completed
0
cumulative oil, bbl
123K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 14, 1983
Shut in
—
Plugged
May 20, 2002

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 -A- G-14-111006Hansford (Morrow, Upper)BP America Production Company10123KJan 1993 – Dec 2002

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. 1Wilbanks Exploration, Inc.Jan 1993 → Aug 1998
  2. 2Amoco Production CompanySep 1998 → Dec 2001
  3. 3Crescendo Resources, L.P.Dec 1998 → Mar 2000
  4. 4BP America Production CompanyJan 2002 → May 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
199618-99DrillTXO Production Corp.Jun 14, 1983Jun 14, 1983—7,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-111006————

Formation tops

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

FormationMD ftSubsea
Tonkawa5,350-2,298
Kansas City5,580-2,528
Des Moines6,080-3,028
Atoka6,704-3,652
Morrow7,095-4,043

Perforations

Perforated and open-hole intervals.

FromToType
7,0967,112Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,73412.251,075 sx
4.57,2007.875550 sx

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
00Jul 26, 1984May 24, 1984—
00Jun 30, 1984May 24, 1984—

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