The 200-Moving-Average Zone: Distinguish a Crash Into It From a Surge Away

Video: I IGNORE MY USUAL TRADING RULES WHEN THIS HAPPENS
Creator: Oliver Velez Trading
Original Video: Watch the original video
Difficulty: Advanced

The Big Idea

A sharp move into a reference area and a sharp move away from it are different events. The source studies both around a 200-period moving average, often looking for a first bounce after a bearish move. The lesson is to define the event and its failure condition without interpreting strong language as permission to abandon risk limits.

Two Locations, One Moving-Average Context

The creator describes a crash into the 200 area that produces a bounce, but may weaken the support enough for a later attempt to continue downward. He separately describes a forceful bearish surge originating near the 200, where the first bounce can offer another observation of continuation.

The first pattern arrives at the reference. The second departs from it. Their diagrams can look similar after the decline has progressed, so mark where the move began before deciding which event is being studied. A large red candle far from the average is not automatically either pattern.

The source repeatedly emphasizes that the moving average is an area rather than a perfectly thin barrier. That is a useful way to avoid treating a one-tick penetration as a universal invalidation. It still requires an explicit zone width if the concept is to be coded or compared consistently.

Powerful Needs a Definition, Not Just a Dramatic Label

The transcript asks for an unmistakably strong, solid move but does not supply a universal numerical threshold. It also suggests mentally combining consecutive candles to understand the total drop. A single-candle body rule and a multi-candle net-move rule will select different examples.

The original indicator uses three consecutive bearish candles with a net decline of at least 1.5 prior ATR and a zone half-width of 0.3 ATR. These are adjustable research definitions, not creator settings. It uses a simple 200-period moving average because the transcript does not specify the exact averaging formula.

A large net move does not identify the amount of money leaving a market. Transactions have buyers and sellers, and price changes do not directly measure net capital departure. Candles can describe the decline’s magnitude and timing without establishing every participant’s intent.

A Bounce Level Is Not a Completed Short Entry

The source discusses dividing a candle into thirds and halves to inspect retracement. Those references describe location within the move. They do not guarantee that a bounce reaching one-third has finished, nor do they automatically define a valid protective stop.

The code freezes the final event candle’s low and high, then displays its one-third and halfway retracement levels. The multi-bar decline qualifies the context, but the displayed fractions use the last candle only. That distinction follows the need to separate the move used for qualification from the candle used for the reference.

A diamond records the first later bar that reaches the one-third level. It deliberately does not claim bearish confirmation. If your execution requires a rejection close, a lower high, or another trigger, define and observe that separately.

The market may never bounce to the deeper reference. It may also reclaim the zone and continue upward. A research comparison must retain both cases, rather than replacing an unfilled deeper entry with the shallower price after seeing that the decline resumed.

Exceptions to a Filter Are Not Exceptions to Risk

The creator says these events can override his usual concerns about support or a trap zone. That is a statement about priority among his chart filters. It should not be interpreted as an instruction to ignore position limits, stops, liquidity, account constraints, or evidence that the event is failing.

The transcript itself qualifies the idea by warning about events late in an already extended decline. A move can satisfy a simple magnitude threshold while being exhausted relative to the larger structure. The proxy does not solve that discretionary context question; a separate extension measure or manual annotation is needed.

The source also suggests greater consistency on the short side while acknowledging a reverse-direction version. No comparative sample is supplied. The companion code is intentionally bearish-only, so it does not establish or compare a long-side edge.

Define When the Observation Ends

A reference that never expires can keep looking useful whenever price eventually returns. The indicator observes one event at a time, cancels it after a completed close above the event high, and expires it after twelve chart bars by default. A later bounce reaching the first reference consumes it.

New qualifying events are ignored while an old one is active, and no same-bar replacement occurs when it resolves. That makes the lifecycle clear but changes the event sample relative to a trader watching every possible crash. Record that selection effect when comparing the code to manual examples.

The SMA and its zone remain plotted even with no active event. The status table explains when the 200-bar history is insufficient or when the script is waiting. The absence of a diamond means the defined later observation has not occurred, not that the reference line is malfunctioning.

A Focused Replay Checklist

1. Origin: did the move start near, above, or far below the zone?
2. Magnitude: what was its net decline relative to information available then?
3. Extension: how much decline preceded the qualifying event?
4. Reference: which candle or whole move supplies thirds and halves?
5. Response: was there a later bounce, and what separate confirmation followed?
6. Failure: what canceled the hypothesis before any intended entry?

Pine Script Indicator

//@version=6
// Guide: https://candlechasers.com/two-hundred-zone-crash-surge-context/
// Original educational approximation; no orders, fills or performance claims.
indicator("CC 200 Zone Crash and Surge Proxy", overlay=true)
length = input.int(200, "SMA period", minval=2)
zoneWidth = input.float(0.3, "Zone half-width / prior ATR", minval=0.01)
power = input.float(1.5, "Minimum three-bar net decline / prior ATR", minval=0.1)
life = input.int(12, "Maximum bounce-observation bars", minval=1)
m = ta.sma(close, length)
a = ta.atr(14)
upper = m + a[1] * zoneWidth
lower = m - a[1] * zoneWidth
// Original multi-bar proxy, NOT a numerical rule disclosed by the creator.
threeRed = close < open and close[1] < open[1] and close[2] < open[2]
powerful = threeRed and open[2] - close >= a[1] * power
crash = powerful and open[2] > upper and low <= upper and high >= lower
surge = powerful and high[2] >= lower[2] and low[2] <= upper[2] and close < lower
var int born = na
var float bounceLow = na
var float referenceHigh = na
var float third = na
var float half = na
var string kind = ""
bool event = false
bool bounce = false
if barstate.isconfirmed
    bool occupied = not na(born)
    if occupied
        if bar_index - born > life or close > referenceHigh
            born := na
        else if bar_index > born and high >= third
            bounce := true
            born := na
    if not occupied and (crash or surge)
        born := bar_index
        bounceLow := low
        referenceHigh := high
        third := low + (high - low) / 3
        half := low + (high - low) / 2
        kind := crash ? "Crash into zone" : "Surge away from zone"
        event := true
plot(m, "SMA 200 proxy", color=color.orange, linewidth=2)
p1 = plot(upper, "Zone upper", color=color.new(color.orange, 70))
p2 = plot(lower, "Zone lower", color=color.new(color.orange, 70))
fill(p1, p2, color=color.new(color.orange, 93))
plot(not na(born) ? third : na, "Event-candle one-third bounce reference", color=color.aqua, style=plot.style_linebr)
plot(not na(born) ? half : na, "Event-candle half bounce reference", color=color.gray, style=plot.style_linebr)
plotshape(event, "Completed crash/surge context", shape.square, location.abovebar, color.red, size=size.tiny)
plotshape(bounce, "Later bounce reaches third: not entry confirmation", shape.diamond, location.abovebar, color.aqua)
alertcondition(bounce, "Bounce observation", "CC: later bounce reached one-third of event candle. No bearish entry confirmation implied.")
var table status = table.new(position.top_right, 1, 1, bgcolor=color.new(color.black, 10))
if barstate.islast
    table.cell(status, 0, 0, na(m) ? "Load at least 200 bars" : na(born) ? "200 zone visible; awaiting qualifying bearish event" : kind + " | observing first bounce", text_color=color.white)

What This Indicator Shows

The indicator always plots a 200-SMA with an ATR-width zone after sufficient history. A red square marks an original three-bearish-bar crash-into or surge-away event. While active, one-third and halfway levels of the final event candle are visible. A later diamond marks reaching the one-third reference only. It consumes the observation; expiry or a completed close above the event high also ends it. All event decisions finalize at candle close.

What This Indicator Does Not Show

It does not reproduce an unspecified source averaging formula, assess every trap-zone exception, measure actual money flows, or mark a confirmed short entry. It omits the bullish mirror model, discretionary stock selection, and a late-move extension filter. The three-bar rule, ATR thresholds, and twelve-bar lifetime are ours. A bounce diamond does not model a fill, stop, target, or trade outcome.

Setup and Validation

Paste the complete script into TradingView’s Pine Editor, save it, and add it to a standard candlestick chart with enough history. Read the status panel and reference plots before expecting a marker. Check the specified chart interval and session inputs. For scripts with alert conditions, use Once Per Bar Close and recreate alerts after changing the code or its settings.

Validation status: Reviewed statically for source-versus-proxy distinctions, completed-bar timing, future-data use, persistent state, reference replacement, expiry, and visible output. This script has not been compiled or chart-tested in TradingView here. No performance or live-execution results are claimed. Use replay to inspect the described behavior; static review does not replace compilation and chart validation.

Research and Replay Lab

These are proposed learning experiments, not results established by the source. Change one main feature at a time, retain failures and missing opportunities, and reserve a later period for evaluation rather than repeatedly selecting settings from the same examples.

Are the two locations different?

Classify crash-into and surge-away events using frozen zone values and a common later-response rule. Keep symbol, timeframe, costs, and management assumptions fixed. Record the categories before seeing the next move and compare their full event populations.

Does prior extension change the response?

Add a predeclared measure such as distance from the prior twenty-bar high in ATR units. Compare low and high extension groups while holding event thresholds constant. This tests the source’s warning about late moves without selecting exceptions afterward.

Which retracement actually fills?

Compare one-third and halfway proposals for the same events. Keep the stop and objective convention fixed. Record missed fills, gaps, actual risk distances, and outcomes; do not award the deeper price when price never reached it.

Check Your Understanding

Is the 200 a guarantee of support? No. It is a reference whose behavior must be observed.

Are crash-into and surge-away identical? No. Their starting locations differ.

Does a bounce diamond mean sell immediately? No. It records location without a separate entry confirmation.

Are the ATR thresholds from the source? No. They are original definitions.

Can an event override risk limits? No. A filter exception does not remove financial constraints.

Final Takeaway

Distinguish where the sharp move began, measure its magnitude consistently, and observe the bounce without assuming it must fail. The source’s priority rules are hypotheses about chart context; test them with explicit lifecycle and risk definitions.

Risk Disclosure

This material is educational and is not personalized financial, investment, or trading advice. Trading can cause substantial losses. Examples, source-reported results, and chart observations do not establish future performance. Hypothetical calculations depend on their assumptions and omit costs unless stated. Spread, fees, slippage, gaps, leverage, liquidity, financing, and contract terms can materially change outcomes. Indicators do not simulate broker execution or establish profitability. Options involve additional contract, expiry, exercise, and valuation risks. Evaluate any approach with appropriate data and realistic risk limits before considering live use.

This is an independent educational companion and is not affiliated with, sponsored by, endorsed by, or authorized by the source creator, channel, or TradingView.