WELLS · TEXAS · ONE ROW PER API NUMBER
Lear Petroleum Exploration Inc. wells
Every well on the Railroad Commission's schedule or with a drilling permit on file, newest permit first: who operates it, where it is, the field it is completed in, its permits, and the last month its lease reported.What an API number is →
A full API number opens the well. Anything else filters the list below.
4 wells match
Production
Well logs are the ones loaded into Petrora from the regulators' log indexes. A log's kind is the regulator's description of it; a digital log is a LAS file of curves. Each well's page lists its logs and links to the regulator for the files.
Texas reports production by lease, so a well carries no volumes of its own: "Last reported" is the last month the lease it is tied to reported. How Texas production is reported →
4 WELLS · PAGE 1 OF 1
These wells on a map →| Well | Operator | County, field | Status | Depth, ft | Permit | Permits | Last reported |
|---|---|---|---|---|---|---|---|
| Murphy #242-269-31074 | Lear Petroleum Exploration Inc. | KingG K (Tannehill) | PluggedOil | 3,600 | Oct 22, 1982 | 1 | — |
| Booth, Lincoln #1-59442-295-31039 | Lear Petroleum Exploration, Inc. | LipscombUnit (U. Morrow) | Drilled | 9,700 | Jul 9, 1981 | 1 | — |
| Stone #142-291-31440 | Lear Petroleum Exploration Inc. | LibertyHathaway (EY-2B) | PluggedOil | 13,348 | Jun 11, 1981 | 1 | — |
| Harris-Beverly #142-313-30314 | Lear Petroleum Exploration Inc. | MadisonMadisonville W. (Austin Chalk) | PluggedOil | 9,900 | Feb 2, 1981 | 1 | — |
About this data
One row per API number: every well on the Railroad Commission wellbore schedule, and every API number a drilling permit names. Operator, field, status, and dates are the schedule's where it lists the well, the latest permit's otherwise. Permits on file counts every permit and amendment. Texas reports production by lease, so a well shows the last month its lease reported and no volumes. Nothing is estimated.
Developers: this page as JSON is GET /v1/data/wells?state=tx, documented in the API reference.