ADVANCED FOREX · ICT · LESSON 09
ICT Kill Zones and Trading Sessions
Learn how trading sessions shape liquidity and volatility, and how to study ICT kill zones without assuming that a time window guarantees a trade.
Learning objectives
- Identify the major forex sessions and overlapping market hours.
- Explain ICT kill zones as observation windows rather than automatic entry signals.
- Recognize how daylight saving changes affect local conversions.
- Build a session journal and a rules-based risk plan.
1. What is a trading session?
Forex activity shifts through the Asia, London and New York business days. Liquidity and volatility can change when large financial centers open, overlap or close. The exact behavior varies by instrument and economic calendar.
| Session | What to observe | Important caution |
|---|---|---|
| Asia | Overnight range, highs and lows, consolidation | Ranges do not always form |
| London | Breaks of prior ranges, possible liquidity runs | A breakout may continue or reverse |
| New York | US data releases, overlap with London, volatility | News can invalidate technical expectations |
2. ICT kill zones
In ICT terminology, a kill zone is a recurring time window traders monitor for liquidity movement and potential setups. Commonly taught windows are expressed in New York local time, not a permanently fixed UTC offset. Different ICT materials may use slightly different boundaries; verify the convention used in your study plan.
Common study windows (New York local time)
- London Open: approximately 2:00–5:00 AM
- New York Open: approximately 7:00–10:00 AM
- London Close: approximately 10:00 AM–12:00 PM
These are study conventions, not guaranteed execution times. Use an America/New_York timezone conversion to account for daylight saving time.
Why Pakistan time changes relative to New York
Pakistan Standard Time stays UTC+5. New York changes between EST (UTC−5) and EDT (UTC−4). Therefore a New York clock-time window appears one hour later in Pakistan during US standard time than during US daylight time. Always confirm the date-specific conversion.
3. Liquidity and session narrative
Mark the prior day high and low, Asian session range, and nearby equal highs/lows. Then observe whether price sweeps a level, displaces away, or simply trends through it. A sweep alone is not a trade signal: seek clear structure, invalidation and a predefined risk limit.
Hypothetical example — not a live signal
- Mark the Asian high and low on a 15-minute chart.
- During London, price briefly trades above the Asian high.
- Wait for a meaningful shift in structure and displacement before forming a bearish hypothesis.
- Define the invalidation level and maximum loss before considering any entry.
- If conditions are unclear or major news is imminent, record “no trade.”
4. A practical session checklist
- Confirm date, New York timezone and any daylight saving adjustment.
- Check the economic calendar and scheduled high-impact releases.
- Mark higher-timeframe direction and obvious liquidity pools.
- Record session range and wait for a valid, testable setup.
- Set position risk and invalidation in advance; do not widen a stop to rescue a trade.
- Screenshot the chart and journal the result, including skipped trades.
5. Practice exercise
Choose five historical trading days for a currency pair. For each day, annotate Asian high/low, London open, New York open and any major news. Note whether a liquidity sweep occurred, whether displacement followed and whether the setup met your rules. Compare observations without assuming every day must produce a trade.
Knowledge check
Session timing: practical execution notes
Session-based models depend on consistent timekeeping. When studying London and New York activity, record the exchange-local timezone and convert it to your chart platform's timezone. Daylight-saving changes in the United States and United Kingdom do not always occur on the same dates, so a fixed local-clock conversion can become wrong for several weeks each year. Confirm the date-specific session time rather than copying a permanent schedule from a social media post.
A useful routine is to mark the previous day's high and low, the overnight range, nearby liquidity pools, and scheduled economic releases before a session begins. During the proposed kill zone, observe whether price sweeps a marked level and whether subsequent displacement supports a directional hypothesis. If price is already far from the nearest logical invalidation point, a late entry may have unattractive risk even if the direction seems correct.
For practice, compare twenty sessions with and without a clear liquidity event. Record the spread at the proposed entry, whether a structure shift formed, and whether the next target was reached before invalidation. Keep screenshots of the losing and ambiguous cases. A kill zone identifies a period to pay attention; it is not itself a buy or sell signal, and it does not remove the possibility of rapid losses.
Applied analysis: testing the lesson in context
The following exercise develops the specific decisions involved in ict kill zones and trading sessions. It is a hypothetical training workflow, not a prediction or an instruction to place a live trade. Keep the market, time zone, instrument, observation window and data source fixed before evaluating the idea. Separate what the chart shows from the interpretation assigned to it; two analysts can label the same sequence differently without either label being a verified market mechanism.
Case step 1: 1. What is a trading session?
Start with the lesson's 1. what is a trading session? component. Source observation: Forex activity shifts through the Asia, London and New York business days. Liquidity and volatility can change when large financial centers open, overlap or close. Record the exact candle or pivot at which this information first became available. If confirmation depends on a later close, mark that later close as the earliest legitimate decision point. A visually compelling retrospective drawing is not sufficient evidence that the setup was identifiable in real time.
Now construct a counterexample for 1. what is a trading session?: imagine the price initially behaves as the lesson suggests but then fails to follow through. Write the invalidation condition as an observable price or time event, not as a vague change in confidence. Compare two annotated screenshots, one before the proposed confirmation and one after it. Explain what genuinely changed in the available evidence. For a trading-system study, record spread, slippage, position size, and whether the proposed stop could have been filled at the assumed price.
Case step 2: 2. ICT kill zones
Start with the lesson's 2. ict kill zones component. Source observation: In ICT terminology, a kill zone is a recurring time window traders monitor for liquidity movement and potential setups. Commonly taught windows are expressed in New York local time , not a permanently fixed UTC offset. Record the exact candle or pivot at which this information first became available. If confirmation depends on a later close, mark that later close as the earliest legitimate decision point. A visually compelling retrospective drawing is not sufficient evidence that the setup was identifiable in real time.
Now construct a counterexample for 2. ict kill zones: imagine the price initially behaves as the lesson suggests but then fails to follow through. Write the invalidation condition as an observable price or time event, not as a vague change in confidence. Compare two annotated screenshots, one before the proposed confirmation and one after it. Explain what genuinely changed in the available evidence. For a trading-system study, record spread, slippage, position size, and whether the proposed stop could have been filled at the assumed price.
Case step 3: Common study windows (New York local time)
Start with the lesson's common study windows (new york local time) component. Source observation: These are study conventions, not guaranteed execution times. Use an America/New_York timezone conversion to account for daylight saving time. Record the exact candle or pivot at which this information first became available. If confirmation depends on a later close, mark that later close as the earliest legitimate decision point. A visually compelling retrospective drawing is not sufficient evidence that the setup was identifiable in real time.
Now construct a counterexample for common study windows (new york local time): imagine the price initially behaves as the lesson suggests but then fails to follow through. Write the invalidation condition as an observable price or time event, not as a vague change in confidence. Compare two annotated screenshots, one before the proposed confirmation and one after it. Explain what genuinely changed in the available evidence. For a trading-system study, record spread, slippage, position size, and whether the proposed stop could have been filled at the assumed price.
Evidence record and independent assessment
Create a small research log specifically labelled “ICT Kill Zones and Trading Sessions”. For each candidate observation, store its date, instrument, session, timeframe, setup definition, entry eligibility, invalidation level, expected costs, and actual subsequent path. Include candidates that never triggered, rather than selecting only attractive examples. Compare at least two market regimes and note whether the interpretation changes when a nearby swing anchor or session boundary is chosen. If it does, classify the result as sensitive to analyst discretion rather than robust evidence.
Finally, write a three-part conclusion about ict kill zones and trading sessions: (1) which elements can be verified directly from historical prices, (2) which elements are hypotheses about participants or future behavior, and (3) what observation would cause you to reject the hypothesis. The exercise is complete only when a second reader could reproduce your markings using the written rules. Do not infer a profitable edge from a single worked example; that requires a separately designed, cost-aware and out-of-sample evaluation.