TEXAS · WELLS · HANSFORD COUNTY · LEMMA LEASE · API 42-195-31178 · DISTRICT 08

Lemma #3

Plugged

Hansford County · Freeman Ranch (Oswego) field  · Vertical

Lemma #3 (API 42-195-31178) is a plugged well in Hansford County, plugged August 22, 2005, last operated by Conocophillips Company.

The RRC has issued one drilling permit, issued June 30, 1993, permitted to 8,285 ft.

It was permitted by Phillips Petroleum Company and has since transferred to Conocophillips Company on the wellbore schedule.

Completion filings report 5 formation tops, including Hugoton, Council Grove, Lansing, Marmaton.

Operator of record

Conocophillips Company

Permitted by Phillips Petroleum Company; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Feb 3, 2026
Permits on file
3,290
Phone
(432) 683-7443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleConocophillips Company
Production reportsPhillips Petroleum Companythrough Jan 1997
Latest permitPhillips Petroleum CompanyJun 30, 1993

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

8,285
total depth, ft
1
permits on file
Jun 30, 1993
last permit issued
Feb 26, 1994
completed
0
cumulative oil, bbl
1.31M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1994 THROUGH Aug 2005

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 26, 1994
Shut in
—
Plugged
Aug 22, 2005

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
Lemma G-14-149034Freeman Ranch (Oswego)Conocophillips Company101.31MFeb 1994 – Aug 2005

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. 1Phillips Petroleum CompanyMar 1994 → Jan 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
413323-99DrillPhillips Petroleum CompanyJun 29, 1993Jun 30, 1993Jul 15, 19938,285

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 26, 1994Lemma G-14-149034Freeman Ranch (Oswego)Conocophillips CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
Hugoton2,718515
Council Grove3,090143
Lansing4,548-1,315
Marmaton5,457-2,224
Oswego5,730-2,497

Perforations

Perforated and open-hole intervals.

FromToType
5,7705,782Perforated
5,7945,805Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,92912.25800 S
5.58,1967.875137 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
00Jul 7, 1994May 27, 1994—
00May 24, 1994Apr 15, 1994Yes
00May 9, 1994——

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