WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-501-33751
Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.
Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.
14 LOG FILES ON 13 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Lackey #242-501-32378Yoakum, TX · Cone & Petree Oil & Gas Exp. Inc | 0.51 | ACOUSTIC POROSITYTIFF | 4,500 to 7,240 | Jul 30, 2012run Jul 6, 1983 |
| Fitzgerald M.T. #242-501-31849Yoakum, TX · Texland Petroleum L.P. | 0.75 | NeutronTIFF | 0 to 8,816 | Oct 1, 2024 |
| Shrek #142-501-37438Yoakum, TX · Texland Petroleum L.P. | 0.86 | Cement BondLAS | 0 to 8,954 | Jun 24, 2026 |
| Shrek #142-501-37438Yoakum, TX · Texland Petroleum L.P. | 0.86 | Gamma RayTIFF | 0 to 8,954 | Jun 24, 2026 |
| Ownby (Clear Fork Upper) Unit #30842-501-32434Yoakum, TX · Occidental Permian Ltd. | 1.10 | NeutronTIFF | 0 to 10,512 | Sep 3, 2021 |
| Ownby (Clear Fork Upper) Unit #30942-501-32411Yoakum, TX · Occidental Permian Ltd. | 1.18 | NeutronTIFF | 100 to 6,900 | Sep 3, 2021 |
| Central Ownby Unit #20642-501-35740Yoakum, TX · Occidental Permian Ltd. | 1.41 | NEUTRON/DENSITY POROSITYTIFF | 4,000 to 7,108 | Aug 21, 2012run Apr 25, 2011 |
| Central Ownby Unit #70842-501-36265Yoakum, TX · Occidental Permian Ltd. | 1.52 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 5,000 to 7,314 | Sep 15, 2014run Mar 4, 2014 |
| Cobb et. al. #2842-501-35300Yoakum, TX · Occidental Permian Ltd. | 1.75 | Neutron/Density PorosityTIFFTHREE DETECTOR LITHO DENSITY COMPENSATED NEUTRON SPECTRAL GAMMA RAY | 200 to 5,436 | May 2, 2007run Apr 24, 2006 |
| Cobb et. al. #2242-501-35307Yoakum, TX · Occidental Permian Ltd. | 1.90 | Neutron/Density PorosityTIFFTHREE DETECTOR LITHO-DENSITY COMP. NEUTRON SPECTRAL GAMMA-RAY | 4,500 to 5,476 | Oct 23, 2007run May 15, 2006 |
| Cobb et. al. #2442-501-35298Yoakum, TX · Occidental Permian Ltd. | 1.92 | Neutron/Density PorosityTIFFYOAKUM | 200 to 5,467 | May 2, 2007run Apr 1, 2006 |
| Kimber 434 #2HHZ42-501-37016Yoakum, TX · Burk Royalty Co. Ltd. | 1.96 | Gamma RayTIFF | 2,450 to 11,042 | Aug 26, 2021 |
| Cobb et. al. #2342-501-35308Yoakum, TX · Occidental Permian Ltd. | 1.97 | Neutron/Density PorosityTIFFTHREE DETECTOR LITHO-DENSITY COMP. NEUTRON SPECTRAL GAMMA-RAY | 200 to 5,452 | Nov 26, 2007run Aug 19, 2006 |
| Ownby San Andres Unit #9542-501-35094Yoakum, TX · Occidental Permian Ltd. | 1.97 | Neutron PorosityTIFFDUAL SPACED NEUTRON SPECTRAL GAMMA LOG | 200 to 5,402 | Jan 30, 2007run Jun 28, 2006 |
About this data
Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.
Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.