WELL · 42-227-34758 · DISTRICT 8
Cline #1
Howard County · Vertical
Cline #1 (API 42-227-34758) is a permitted well in Howard County filed by Baytech, Inc.; no completion report is on file yet.
The RRC has issued 2 drilling permits (amended once) between 1993 and 1996, permitted to 10,400 ft.
Completion filings report 5 formation tops, including Yates, Clear Fork, Spraberry, Dean.
Its lease has reported 29.3K barrels of oil and 46.5K mcf of gas since July 1993, last reporting in August 2007.
Operator of record
Midland, TX · P-5 Y, filed Oct 4, 2002 · 203 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Schlagal, Inc.through Dec 2002 |
| Latest permit | Baytech, Inc.Feb 20, 1996 |
- 10,400
- total depth, ft
- 3
- permits on file
- Feb 20, 1996
- last permit issued
- —
- completed
- 29.3K
- cumulative oil, bbl
- 46.5K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 1993 THROUGH Aug 2007
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Cline O-10-33891 | Knott, SE. (Wolfcamp) | Smith Pipe of Abilene | 1 | 29.3K | 46.5K | Jul 1993 – Aug 2007 |
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.
- 1Baytech, Inc.Jul 1993 → Aug 2001
- 2Schlagal, Inc.Sep 2001 → Dec 2002
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 444951-99 | Recompletion | Baytech, Inc. | Feb 20, 1996 | Feb 20, 1996 | — | 9,300 |
| 412219-98 | Drill | Baytech, Inc. | Jul 21, 1993 | May 27, 1993 | — | 8,880 |
| 412219-99 | Drill | Baytech, Inc. | May 27, 1993 | May 27, 1993 | Jun 9, 1993 | 10,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-10-33891 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,616 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,830 | 8,880 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 357 | 17.5 | 375 S |
| 8.625 | 3,502 | 11 | 2,180 S |
| 5.5 | 8,887 | 7.875 | 600 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Aug 23, 1993 | Jul 21, 1993 | Yes |
| 00 | Jul 27, 1993 | — | — |
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.
- Wellbore filings for 42-227-34758 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-227-34758 → scanned completion filings
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/22734758, documented in the API reference.