WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-371-00554
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.
16 LOG FILES ON 15 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Priest & Beavers Unit #3242-371-38833Pecos, TX · New Height Energy LLC | 0.12 | NeutronTIFF | 0 to 2,445 | Nov 27, 2017 |
| Priest & Beavers Unit #3342-371-38834Pecos, TX · New Height Energy LLC | 0.13 | Gamma RayTIFF | 0 to 2,437 | Oct 3, 2018 |
| Priest & Beavers Unit #14W42-371-38513Pecos, TX · New Height Energy LLC | 0.24 | NEUTRON POROSITYTIFF | 1,400 to 2,414 | Sep 20, 2010run Sep 21, 2009 |
| Priest & Beavers East State Unit #1042-371-39119Pecos, TX · New Height Energy LLC | 0.39 | RESISTIVITYTIFF | 888 to 2,508 | Dec 21, 2016run Dec 11, 2013 |
| Priest & Beavers Unit #3542-371-38973Pecos, TX · New Height Energy LLC | 0.40 | NEUTRON POROSITYTIFF | 0 to 2,496 | Dec 2, 2016run Nov 21, 2013 |
| Priest & Beavers Unit #3142-371-38832Pecos, TX · New Height Energy LLC | 0.43 | NEUTRON/DENSITY POROSITYTIFF | 200 to 2,421 | Oct 7, 2014run Oct 4, 2011 |
| Priest & Beavers Unit #10042-371-39105Pecos, TX · New Height Energy LLC | 0.50 | NEUTRON POROSITYTIFF | 0 to 2,335 | Dec 7, 2016run Nov 8, 2013 |
| Priest & Beavers Unit #1042-371-37603Pecos, TX · New Height Energy LLC | 0.58 | NEUTRON POROSITYTIFF | 2,050 to 2,320 | Jun 25, 2009run Jul 17, 2006 |
| Priest & Beavers Unit #26W42-371-38504Pecos, TX · New Height Energy LLC | 0.58 | NEUTRON POROSITYTIFF | 1,400 to 2,425 | Sep 27, 2010run Sep 21, 2009 |
| Priest & Beavers Unit #20W42-371-38503Pecos, TX · New Height Energy LLC | 0.83 | NEUTRON POROSITYTIFF | 1,370 to 2,386 | Sep 27, 2010run Oct 9, 2009 |
| Priest & Beavers Unit #942-371-37602Pecos, TX · New Height Energy LLC | 0.88 | NEUTRON POROSITYTIFF | 1,950 to 2,317 | Jun 25, 2009run Jul 17, 2006 |
| Priest & Beavers Unit #10242-371-39216Pecos, TX · New Height Energy LLC | 1.13 | NEUTRON POROSITYTIFF | 50 to 2,357 | May 26, 2017run Jun 25, 2014 |
| Priest & Beavers Unit #17W42-371-38501Pecos, TX · New Height Energy LLC | 1.22 | NEUTRON POROSITYTIFF | 1,300 to 2,306 | Sep 27, 2010run Oct 7, 2009 |
| Priest & Beavers Unit #10342-371-39215Pecos, TX · New Height Energy LLC | 1.25 | NEUTRON POROSITYTIFF | 800 to 2,295 | Jul 31, 2017run Aug 26, 2014 |
| Priest & Beavers Unit #20042-371-39249Pecos, TX · New Height Energy LLC | 1.63 | RESISTIVITY2 TIFF | 0 to 2,189 | Sep 1, 2017run Sep 29, 2014 |
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.