WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-417-04552

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.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-417-04552Clear

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.

18 LOG FILES ON 15 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Newell W. P. -C- #942-417-38693Shackelford, TX · 5L Properties Inc.0.11RESISTIVITYTIFF100 to 1,630Dec 5, 2008run Aug 18, 2007
Newell W. P. -C- #842-417-38515Shackelford, TX · 5L Properties Inc.0.17Neutron/Density PorosityTIFFCOMPENSATED DENSITY NEUTRON MICROLOG1,286 to 1,836Jan 28, 2008run Sep 16, 2005
Newell W. P. -C- #842-417-38515Shackelford, TX · 5L Properties Inc.0.17ResistivityTIFFDUAL INDUCTION FOCUSED LOG50 to 1,836Jan 28, 2008run Sep 16, 2005
Newell W. P. -C- #1042-417-38692Shackelford, TX · 5L Properties Inc.0.23NEUTRON/DENSITY POROSITYTIFF700 to 1,671Apr 2, 2009run Jul 11, 2007
Newell W. P. -C- #1042-417-38692Shackelford, TX · 5L Properties Inc.0.23RESISTIVITYTIFF100 to 1,673Apr 2, 2009run Jul 11, 2007
Newell W. P. -a- #442-417-38694Shackelford, TX · 5L Properties Inc.0.32NEUTRON/DENSITY POROSITYTIFF1,200 to 1,645Jun 14, 2010run May 30, 2007
Newell W. P. -a- #442-417-38694Shackelford, TX · 5L Properties Inc.0.32RESISTIVITYTIFF100 to 1,645Jun 11, 2010run May 30, 2007
Davis Merrick a #1642-417-03587Shackelford, TX · United Operating LLC1.64RESISTIVITYTIFF130 to 1,792Feb 22, 2010run Dec 9, 2008
Davis Merrick #842-417-38665Shackelford, TX · United Operating LLC1.77RESISTIVITYTIFF100 to 1,445Oct 26, 2009run Feb 6, 2007
Davis Merrick #942-417-38657Shackelford, TX · United Operating LLC1.82RESISTIVITYTIFF50 to 1,500Oct 20, 2008run Jan 8, 2007
Davis Merrick #442-417-38624Shackelford, TX · United Operating LLC1.83RESISTIVITYTIFF50 to 1,485Sep 30, 2008run Aug 18, 2006
Davis Merrick #142-417-38625Shackelford, TX · United Operating LLC1.84ResistivityTIFFDUAL INDUCTION FOCUSED LOG50 to 1,501May 30, 2007run Aug 9, 2006
Davis Merrick #5__42-417-38655Shackelford, TX · Boo-Row Pipe & Supply Inc.1.85RESISTIVITYTIFF50 to 1,235Oct 28, 2008run Nov 17, 2006
Davis Merrick #1142-417-38669Shackelford, TX · United Operating LLC1.88RESISTIVITYTIFF100 to 1,520Jun 18, 2009run Feb 20, 2008
Davis Merrick #1342-417-38679Shackelford, TX · United Operating LLC1.90RESISTIVITYTIFF100 to 1,505Sep 24, 2008run Mar 26, 2007
Davis Merrick #1542-417-38681Shackelford, TX · United Operating LLC1.91RESISTIVITYTIFF940 to 1,481Jun 18, 2009run Feb 11, 2008
Davis Merrick #742-417-38656Shackelford, TX · United Operating LLC1.91ResistivityTIFFDUAL INDUCTION LOG50 to 1,237May 30, 2007run Dec 11, 2006
Davis Merrick #1242-417-38680Shackelford, TX · United Operating LLC1.93RESISTIVITYTIFF100 to 1,500Sep 18, 2008run Apr 12, 2007

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.